test

Sun Java System Application Server Enterprise Edition 8.2 Release Notes for Microsoft Windows

Administration

This section describes known administration issues and associated solutions.

Load Balancer Feature Not Supported With Application Server in Configure Automatically During Installation Option (6463858)

The loadbalancer feature is not supported with Application Server in Configure Automatically During Installation option.

Workaround:The loadbalancer feature can be configured after Application Server installation.

Note –

You need to have Application Server and Web Server installed on your system to configure the loadbalancer feature.

    To configure the loadbalancer feature, follow these steps:

  1. Set the value of IS_LB to true and Cfgr_LB to false value in the registry HKEY_LOCAL_MACHINE -> Sun Microsystem -> EntSys -> Installer -> Application Server.

  2. Change to the setup directory.

    cd JavaES-Install-Dir\setup\ 


    
    		

    

    


    3. 

  3. 

    Run the ASConfigure.bat batch file.
    



    4. 

  4. 

    Follow the instructions and provide the appropriate value.
    


    
Note – 

    For AS_LB Plug-in, type Sun Java System Web Server [Mandatory]
as this is the only supported plug-in under Java ES 5.
    


    



    5. 

  5. 

    Reboot the system.
    



    6. 




package-appclientScript Not Working if domain1 is Missing (ID 6171458)


By default, a hard-coded value is in JavaES-Install-Dir\lib\lib\package-appclient.xml for the AS_ACC_CONFIG variable for domain1 that is pointed to by asenv.conf. If domain1 is deleted and a new domain
created, the AS_ACC_CONFIG variable is not updated with
the new domain name, which causes the package-appclient script
to fail.


Solution


Do one of the following:



Installing the Load Balancing Plug-in Overwrites an Existing Plug-in (ID 6172977)


If you install the Load Balancing plug-in against an installation of the Application Server that
already has a load balancing plug-in installed (for example,
from 7.1EE), the 8.2EE plug-in silently replaces any existing load balancer, even if you have
created a new server instance in which to run the plug-in.


The plug-in
files are installed by default under the install_dir/plugins/lbplugin directory, which means that only one version
of a plug-in
can be used with any one Application Server installation. Note that the console
installer does display a message indicating that an uninstallation is being performed,
but this message can easily
be missed.


Solution


Not everyone will encounter this problem. If you do encounter the problem,
remove the old Application Server installation and perform a fresh installation rather than performing an upgrade installation.


Several Changes in asadmin Script in Java ES3 Application Server 8.2 compared
to Java ES2 Application Server 7 (ID 6189433, 6189436)


Several changes have
been made to the asadmin command in Application Server 8.2 compared
to Application Server 7 and
compatible versions. For example, Application Server 7 and compatible versions the command to start a server instance is as follows:









asadmin start-instance





In version 8.2, the equivalent command is as follows:









asadmin start-domain --user admin domain1





Refer to the following documents for complete information about the
latest asadmin command syntax:



Default Ports Changed in Application Server (ID 6198555)


When upgrading to Java ES5Application Server 8.2 from
Java ES2Application Server 7and compatible versions,
you might experience
incompatibilities or errors because the default ports have changed.


Cannot Restore Backed-up Domain With Another Name. (ID 6196993)


Mirroring of a domain on the same Application Server installation cannot
be performed by using the backup-domain and restore-domain commands because the domain cannot be restored by using a different name
than the original, even though the asadmin restore-domain command
provides an option to rename the domain. Renaming the backed-up domain appears
to succeed, but attempts to start the renamed domain fail because the entries
in the domain configuration are not changed, and startserv and stopserv use the original domain name to set paths.


Solution


The domain name used for restore-domain must be the
same as that used for the original backup-domain command.
The backup-domain and restore-domain commands
in Application Server 8.2 work only for backing up and restoring the same
domain on the same machine.


Starting Application Server With Additional JMX Agent Not Supported (ID 6200011)


J2SE 1.4., 5.0, and compatible versions can be configured
on the Application Server. An integral feature of the J2SE 5.0 platform is the ability to
start a JMX agent. This agent is activated when you explicitly set system properties at the server
startup.


Example values include
the following:


name="com.sun.management.jmxremote" value="true"
name="com.sun.management.jmxremote.port" value="9999"
name="com.sun.management.jmxremote.authenticate" value="false"
name="com.sun.management.jmxremote.ssl" value="false"


After configuring JMX properties and starting the server, a new jmx-connector server is started within the Application Server VM. An undesirable side-effect
of this is that the administration functions are affected adversely, and the Application Server administration
GUI and CLI might produce
unexpected results. These
results are caused by some conflicts
between the built-in jmx-connector server and the new jmx-connector server.


Solution


If using jconsole or any other JMXcompliant client, consider reusing the
standard JMX Connector Server that is started atApplication Server startup.


When the server starts, a line similar to the one shown in the next paragraph appears
in the server.log. You can connect to the JMXServiceURL specified there and perform the same management and configuration operations
after successfully providing the credentials, for example:


[#|2004-11-24T17:49:08.203-0800|INFO|sun-appserver-ee8.1|javax.enterprise.
system.tools.admin|_ThreadID=10;|ADM1501: Here is the JMXServiceURL for the 
JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://hostname:8686/management/
rmi-jmx-connector]. This is where the remote administrative clients should 
connect using the JSR 160 JMX Connectors.|#]


For more information, refer to the Sun Java System Application Server 8.2 Administration
Guide.


Load Balancer Configuration File  Not Created With the Endpoint URL of Any Web Service (ID 6236544, 6275436)


When setting up the load balancer configuration with an application
that has an EJB module that exports a web service URL, the context root for
the web service isnot in the resulting loadbalancer.xml file.


Solution


    

  1. 

    Edit the loadbalancer.xml file to add
the missing web module as follows:
    


    

    


    

    <web-module context-root="context-root-name"
disable-timeout-in-minutes="30" enabled="true"/>
    
    		

    

    


    2. 

  2. 

    Replace context-root-name value
with the context root name of the web service that was exposed as an EJB.
    



    3. 



Java Home Setting Inside Configuration Not Effective (ID 6240672)


Application Server domains and servers do not use the JDK that is pointed by the java-home attribute
of java-config element of the associated configuration.


Solution


The JDK used by the Application Server processes for all the domains
in a given server installation is determined by the appserver-installation-dir/config/asenv.conf file. The property AS_JAVA in this file determines the JDK used and is set at the time of
installation. If a different JDK is to be used by Application Server processes
after the installation is completed, this value can be modified to point to
another JDK. Note that all domains in this installation are affected by this change.


Note – 
Manual changes to asenv.conf file are not checked
for validity, so be
cautious while changing them. Check
the product documentation for minimum JDK version requirements when modifying
the value for AS_JAVA.




Application Server Restart Using sun-appserv-admin Causes LoginException Error (ID 6288893)


This problem is caused by a wrong value for %CONFIG_HOME%.


Solution


    

  1. 

    Rename the existing asantto asant.bak.
    



    2. 

  2. 

    Copy the asant.template file in as_install/lib/install/templates/ee for SE or EE version to the as_install/bin/ directory and rename the asant file.
    



    3. 

  3. 

    Edit the newly copied as_install/bin/asant file,
replacing the %CONFIG_HOME% token with as_install/config value.
    



    4. 

  4. 

    If any manual changes were made to the original asant.bak file,
merge them into the new asant file.
    



    5. 




.asadmintruststore File Not Described in the Application Server Documentation (ID 6315957)


If this file does not exist in the server administrator's home directory,
you might experience
serious bugs when upgrading certain applications hosted on the server.


Solution



Domain Fails to Start When create-domain Master Password Has Special Characters (ID 6345947)


The domain does not start when
the domain's master password contains the percent (%) character.


Solution


The domain's master password should not contain a percent character
(%). This solution applies when creating a new domain
or changing the master password for an existing domain.


Load Balancer Configuration Changes in magnus.conf and obj.conf Are Overwritten (ID 6394181)


After you have
created a secure http-listener and installed lbplugin,
the magnus.conf and obj.conf files
under the webserver_instance_dir/config directory are modifiedand the lbplugin contents are being removed.


The installer modifies the magnus.conf and obj.conf configuration files on the Application Server as part of the installation
of the load balancer plug-in. If you log in to the Application Server admin console and try to
manage the instance configuration for the instance on which the load balancer
has been installed, the Application Server issues a warning message stating that it
has detected a manual edit in the configuration. This warning is in fact referring
to the changes made by the installer.


Solution


Verify that the changes made by the installer have not been overwritten.