Sun GlassFish Enterprise Server 2.1 Release Notes

Chapter 3 Known Issues and Limitations

This chapter describes known problems and associated workarounds for the Sun GlassFish Enterprise Server 2.1 software. If a summary statement does not specify a particular platform, the problem applies to all platforms.

This information is organized into the following sections:


This section describes known administration issues and associated solutions.

Stand-alone instances sometimes obtain files from other instances (6698604)


In some circumstances, files installed on the DAS intending to be synchronized with a specific instance actually get sent to additional instances.


No known solution.

Startup Message from the start-cluster command are too verbose (6728317)


The asadmin start-cluster command shows too many messages even when non-critical components fail during startup. See the following example command output when non-critical elements (related to the instances in the cluster) fail:

./asadmin start-cluster --port 9898 cluster1
Please enter the admin user name>admin
Please enter the admin password>
The clustered instance, instance2, was successfully started.
error 0 [#|2008-07-17T14:58:16.496+0200|WARNING|sun-appserver9.1|javax.jms|
Error occurred on connection creation [localhost:37676]. - cause: Connection refused|#]

error 1 [#|2008-07-17T14:58:17.517+0200|WARNING|sun-appserver9.1|javax.jms|
Error occurred on connection creation [localhost:37676]. - cause: Connection refused|#]

error 2 [#|2008-07-17T14:58:30.596+0200|WARNING|sun-appserver9.1|
|EJB5108:Unable to initialize EJB Timer Service. 
The likely cause is the database has not been 
started or the timer database table has not been created.|#]

error 3 [#|2008-07-17T14:58:32.512+0200|WARNING|sun-appserver9.1|
RAR5005:Error in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

The clustered instance, instance1, was successfully started.
error 0 [#|2008-07-17T14:58:21.117+0200|WARNING|sun-appserver9.1|
|EJB5108:Unable to initialize EJB Timer Service. The likely cause is the database has 
not been started or the timer database table has not been created.|#]

error 1 [#|2008-07-17T14:58:23.106+0200|WARNING|sun-appserver9.1|
|RAR5005:Error in accessing XA resource with JNDI name [__CallFlowPool] for recovery|#]

Command start-cluster executed successfully.


No known solution. These (exceptions) messages can be ignored.

Failed to Deploy Generic RA Resource Adapter against IBM MQ (Issue 6605)


Deployment of a generic RA adapter against IBM Message Queue product fails. The permissions granted in the server.policy file is as follows.

grant {
      permission java.util.logging.LoggingPermission "control";
      permission java.util.PropertyPermission "*", "read,write";


Change the permissions in the server.policy file as follows:

grant codeBase
"file:${com.sun.aas.installRoot}/lib/install/applications/adminapp/-" {
  permission java.util.logging.LoggingPermission "control";

The package-appclient script does not work if domain1 is not present (6171458)


By default, there is a hard-coded value in as-install/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.


Do one of the following:

  1. Leave domain1 intact, and create your other domains around it.

  2. Remove domain1 and replace the hard-coded value for domain1 in as-install/lib/package-appclient.xml with the new domain name.

This will have to be done every time a new domain is created if domain1 is not present.

Starting the Server with additional JMX Agent is not supported (6200011)


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

Example values include:

name="" value="true"
name="" value="9999"
name="" value="false"
name="" value="false"

After configuring JMX properties and starting the server, a new jmx-connector server is started within the Virtual Machine. An undesirable side-effect of this is that the administration functions are affected adversely, and the Administration Console and command—line interface may produce unexpected results. The problem is that there are some conflicts between the built in jmx-connector server and the new jmx-connector server.


If using jconsole (or any other JMX-compliant client), consider reusing the standard JMX Connector Server that is started with server startup.

When the server starts up, a line similar to the one shown below appears in the server.log. You can connect to the JMXService URL specified there and perform the same management/configuration operations after successfully providing the credentials; for example:

Here is the JMXServiceURL for the JMXConnectorServer: 
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 GlassFish Enterprise Server 2.1 Administration Guide.

Load balancer configuration file does not get created with the endpoint URL of any web service (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 isn't in the resulting loadbalancer.xml file.


  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. Replace context-root-name value with the context root name of the web service that was exposed as an EJB.

.asadmintruststore file not described in the Enterprise Server documentation (6315957)


The .asadmintruststore file is not described in the Enterprise Server documentation. If this file does not exist in the server administrator's home directory, you may experience serious bugs when upgrading certain applications hosted on the server.


Clustered instances fail to start due to a timeout in reaching the JMS broker (6523663)


The default MQ integration mode for a Enterprise Server cluster instance is LOCAL. When Enterprise Server is installed in a location (PATH) that is long (read “not short”), imqbrokerscv.exe crashes when the cluster instance starts. The problem is a memory allocation problem in imqbrokersvc.


The JMS service type for the cluster instance must be changed from the default LOCAL to REMOTE. In this configuration, all the instances point back to the DAS broker. Follow the instructions below to configure a cluster in REMOTE mode.

Note –

When using REMOTE mode, all instances are using one broker (DAS) , and therefore no broker cluster is created when the Enterprise Server cluster starts up. See “Auto-clustering” in Section 4.1, Division iii of the one-pager at for more information. The above functionality will not be available!

ProcedureUsing the command-line

Before You Begin

Modify the port and password file according to your environment. Note that in the instructions below, the cluster name is racluster, the DAS admin port is 5858, and the DAS JMS port is 7676.

  1. Modify the cluster configuration, changing the JMS type to REMOTE.

    as-install/bin/asadmin.bat set --port 5858 --user admin --passwordfile \
    as-install/bin/password_file racluster.jms-service.type=REMOTE
  2. Create a JMS host corresponding to the DAS JMS host.

    as-install/bin/asadmin.bat create-jms-host --port 5858 --user admin --passwordfile \
    as-install/bin/password_file --target racluster --mqhost localhost --mqport 7676 \
    --mquser admin --mqpassword admin dashost
  3. Set the default JMS host to be the DAS JMS host created in the previous step.

    as-install/bin/asadmin.bat set --port 5858 --user admin --passwordfile \
    as-install/bin/password_file racluster.jms-service.default-jms-host=dashost

ProcedureUsing the Admin GUI

  1. Go to Configurations->cluster-name-config->Java Message Service->JMS Hosts.

  2. Click New to create a new JMS host; name it dashost.

  3. Enter configuration settings corresponding to the JMS service for the DAS; defaults are as follows:

    • Hostname: localhost

    • Port: 7676

    • Admin user: admin

    • Password: admin

    Modify these settings as appropriate for your DAS JMS service.

  4. Navigate back to the Java Message Service tab, and change the JMS service type to REMOTE (default is LOCAL).

  5. Choose dashost from the default-jms-host drop-down list.

  6. Save the changes, and then start your node-agent or cluster.

Cannot display jmaki chart in Netscape 8.1.3, Mozilla 1.7 and Safari 2.0.4 browsers (6543014)


When trying to display a chart from the Log Statistics Monitoring page using some unsupported browsers, the following error may be thrown:

Error loading jmaki.widgets.jmaki.charting.line.Widget : id=form1:jmaki_chart11
Script: \
line/component.js (line:5437).
Message: area.initialize is not a function


Use a supported browser. Refer to Browsers for a list of browsers supported by Enterprise Server 2.1.

Default ports changing in each AS major release (6566481)


The default admin port has changed in each of the past three major Enterprise Server releases. Specifically, the default admin ports in 7.x, 8.x, and 9.x are as follows:


This is not a bug, but something to be aware of. The default admin port is just a recommendation. It is anticipated that future Enterprise Server releases going forward will retain the default 4848 port.

The create-domain command fails with custom master password in AIX (6628170)


On the AIX operating system, an attempt to create a domain with a custom master password fails with the following error:

keytool error (likely untranslated): java.lang.NullPointerException
 Enter keystore password:  New keystore password:

ProcedureSolution: (AIX) To Create a Domain With a Custom Master Password

Note –

In the procedure that follows, only the options that are required in each step are provided. If you require additional options for a command, specify these options in the command. For information about Enterprise Server commands, see Sun GlassFish Enterprise Server 2.1 Reference Manual.

  1. Create a shell script that contains the following lines of code:

    changeKeystorePass() {
      keytool -storepasswd -keystore ${KEYSTORE} -storepass ${OLD} -new ${NEW}
    changeTruststorePass() {
      keytool -storepasswd -keystore ${TRUSTSTORE} -storepass ${OLD} -new ${NEW}
    changeKeyPass() {
      keytool -keypasswd -alias s1as -keystore ${KEYSTORE} -storepass ${NEW} -keypass ${OLD} -new ${NEW}
    changeDomainPasswordEntry() {
      keytool -storepasswd -storetype JCEKS -keystore ${DOMAINPASSWORDS} -storepass ${OLD} -new ${NEW}
    deleteMasterPasswordFile() {
      if [ -f ${DOMAIN_PATH}/master-password ] ; then
        echo Deleting ${DOMAIN_PATH}/master-password
        rm -f ${DOMAIN_PATH}/master-password
    if [ $# != 3 ] ; then
      echo Usage: $0 domain-path old-master-pass new-master-pass
      exit 1
    echo Processing ...
    if [ ! -f ${DOMAIN_PATH}/config/domain.xml ] ; then
      echo "Domain with folder ${DOMAIN_PATH} does not exist, create it first"
      exit 2
  2. Create a domain, specifying the default master password.

    aadmin create-domain {--adminport aminportno|--portbase portbase} domain-name
    Please enter the admin user name>admin-user
    Please enter the admin password>admin-user-password
    Please enter the admin password again>admin-user-password
    Please enter the master password [Enter to accept the default]:>
    Please enter the master password again [Enter to accept the default]:>

    The default master password is changeit.

  3. Change the master password of the domain that you have just created.

    To change the master password, run the script that you created in Step 1.

    script-name domain-path old-password new-password
  4. Start the domain that you created in Step 2.

    asadmin start-domain domain-name

    Because the domain has a custom master password, you are prompted for the master password.

  5. In response to the prompt, type the new master password.

  6. For domains that are configured to support clusters, create and start a node agent.

    1. Create a node agent for the domain that you created in Step 2.

      asadmin create-node-agent --port portno --user admin-user
    2. Start the node agent that you created in Step a.

      asadmin start-node-agent

      Because the domain has a custom master password, you are prompted for the master password.

    3. In response to the prompt, type the new master password.

See Also

The following Enterprise Server man pages:

AIX: 0403-027 The parameter list is too long (6625591)


On the AIX operating system, some OS-related operations might fail with the following error:

0403-027 The parameter list is too long

Examples of OS-related operations are deploying applications or running the application client container.

This issue is commonly caused by long file paths in the CLASSPATH environment variable.


Use one of the following solutions:

Procedure(AIX) To Increase the Maximum Length of the Command Line

The ncargs attribute determines maximum length of the command line, including environment variables. On the AIX operating system, the default value of the ncargs attribute is four, 4–Kbyte blocks. To ensure that Enterprise Server commands do not exceed the maximum length of the command line , increase this value to 16 4–Kbyte blocks.

Note –

After the value of the ncargs attribute is changed, no reboot or refresh of daemons is required.

  1. Determine the value of the ncargs attribute.

    lsattr -EH -l sys0 | grep ncargs
  2. If the value of the ncargs attribute is less than 16 4–Kbyte blocks, increase the value to 16.

    chdev -l sys0 -a ncargs=16

In Bourne shell, all DAS, node agent, and instance processes exit when console window is closed. (6879701)


If you log in as root with the Bourne shell (/bin/sh) and run asadmin commands, then log out of the console window, all the domain administration server (DAS), node agent, and instance processes are killed. This is because in the Bourne shell all child terminals inherit the TTY by default, so when the terminal is logged out, all child processes are killed too.


Before running any asadmin commands, do the following:

  1. Log in to the server.

  2. Change to K shell:

    # exec /bin/ksh
  3. In K shell, run all the asadmin commands to bring up the DAS, node agents, and instances.

Apache and Load Balancer Plugin

This section describes known Apache Web server and load balancer plugin issues and associated solutions.

Deployment of Java EE application with EJB as a Web Service is not captured by load balancing plug-in (Issue 685)


When you deploy any WAR (or EAR) with a servlet-based web service, the HTTP Load Balancer is updated with information about the web service. When an EJB-based web service is deployed, the configuration of the HTTP Load Balancer is not updated to reflect the new object.


Add these context roots manually to the load balancer configuration file (loadbalancer.xml). However, dynamic reconfiguration of load balancer configuration (using the auto-apply feature) would result in older manual edits being lost.

Turn off the auto-apply feature from DAS and instead use the manual export feature to edit and apply the load balancer configuration onto the Web Server.

The High-Availability Administration Guide does not contain instructions for using a certificate for Apache 2.0 (6307976)

To run Apache security, you must use a certificate. For instructions on obtaining a certificate from a certificate authority, see the information on certificates in the modssl FAQ.

Must start Apache Web Server as root (6308021)

On Solaris, if your Application Server was installed under root, you must start the Apache Web Server as root. Java Enterprise System installations are installed as root. For Apache 2.0, after starting as root, Apache switches and runs as another user you designate. You designate that user in the /conf/httpd.conf file. To start as root, on many systems you must edit the httpd.conf file to designate the correct group. Replace the line:

Group #-1


Group nobody

More information on user/group use is included in the httpd.conf file.

Application Client

This section describes known application client issues and associated solutions.

Library JAR packaged in Application Client Archive overwrites MANIFEST file (6193556)


If you have a top level JAR file inside your client JAR (in this case, reporter.jar), when you deploy the client JAR, the MANIFEST file for that JAR overwrites the MANIFEST file for the client JAR.


None at this time.

ACC always tries to connect to localhost:3700 (6527987)


The application client always tries to connect to localhost:3700. The problem is that several system properties need to be read before the client code is invoked.


Set the following as system properties (-D in your JAVA_CMD). Do not set them in your appclient code:

org.omg.CORBA.ORBInitialHost = server-instance-host
org.omg.CORBA.ORBInitialPort = server-instance-port

Unable to start domain , missing sunpkcs11.jar (6571044)


Running on 64–bit Linux, the following exception when starting a domain. The issue is a missing sunpkcs11.jar under jdk1.5.0_11/jre/lib/ext/.


This is a known JDK bug with 64–bit Linux, and will be fixed in JDK 1.5.0_13.

ASQuickStartup breaks SocketChannel.keyFor(), returning null instead of the SelectionKey (Issue Tracker 3027)


When a SocketChannel is registered on several Selectors, doing socketChannel.keyFor(lastRegisteredSelector) returns null instead of the SelectionKey.


This is related to a JDK bug, 6562829, and is expected to be fixed in 6.0 U3. A workaround has been included in Enterprise Server 2.1, such that the selector is unwrapped before the keyFor API is called. This enables the keyFor to succeed until JDK bug is fixed.

Bundled Sun JDBC Drivers

This section describes known bundled Sun JDBC driver issues and associated solutions.

PreparedStatement errors (6170432)

Description 1

If an application generates more than 3000 PreparedStatement objects in one transaction, the following error may occur with DB2:

[sunm][DB2 JDBC Driver] No more available statements.Please recreate your package with a larger dynamicSections value.

Solution 1

Add following properties to the connection pool definition to get the driver to rebind DB2 packages with a larger dynamic sections value:

createDefaultPackage=true replacePackage=true dynamicSections=1000

See the Sun GlassFish Enterprise Server 2.1 Administration Guidefor details about configuring connection pools.

Description 2

Related to the PrepardStatement error above, another error message that may be thrown is:

[sunm][DB2 JDBC Driver][DB2]Virtual storage or database resource is not available.

Solution 2

Increase the DB2 server configuration parameter APPLHEAPSZ. A good value is 4096.

Description 3

Isolation level TRANSACTION_SERIALIZABLE. If your application uses isolation level TRANSACTION_SERIALIZABLE and uses one of the parameters suggested above, it might hang while obtaining a connection.

Solution 3

To set desired isolation level for a connection, the corresponding connection pool has to be created at that isolation level. See the Sun GlassFish Enterprise Server 2.1 Administration Guide for instructions.

Java DB is not started after machine reboot or server start (6515124)


The bundled Java DB database is not automatically restarted after a host system or Solaris zone reboot, or an Enterprise Server start. This is not a bug, but expected behavior for any bundled or third-party application. The problem is that the Java DB must be started before the Enterprise Server instance.


After rebooting the host machine or Solaris zone, be sure to start the Java DB before starting Enterprise Server; for example:

/opt/SUNWappserver/appserver/bin/asadmin start-database

Refer to Administration Tools in Sun GlassFish Enterprise Server 2.1 Quick Start Guide in the Sun GlassFish Enterprise Server 2.1 Quick Start Guide for more information about asadmin command options.


Autodeployment fails on a cluster sometimes (6610527)


Timing issues sometimes cause autodeployment to fail in domains that are configured to support clusters. The issue is not observed in domains that do not support clusters.


Use one of the following solutions:

Bundled ANT throws java.lang.NoClassDefFoundError (6265624)


The following exception is thrown in thread "main" java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/Launcher.


Use of the bundled ANT for things outside the Enterprise Server is not recommended.

Application specific classloader not used by JSP compilation (6693246)


The application-specific classloader (applibs or --libraries) is not used by the JSP compilation. As a result, JSPs referencing these JARs will not compile.


No known solution.


This section describes known documentation issues and associated solutions.

Javadoc Inconsistencies (various IDs)

The Javadoc for several AMX interfaces and methods is either missing or incorrect:

Online help does not describe how to create a JMS physical destination for a specific server instance or cluster. (6808339)


Use the following procedure to create configuration-specific JMS physical destinations:

  1. Log on to the Admin Console.

  2. In the left-hand pane, click Standalone Instances > instance_name. If you are using clusters, click Clusters > cluster_name.

  3. Click the JMS Physical Destinations tab.

  4. Click New.

  5. Create a Queue and Topic.

Operand is missing from man page example for ping-connection-pool. (6881540)

The example in the man page is missing the operand at the end of the command. An error occurs if the command is entered as shown in the example. Correct example is:

asadmin> ping-connection-pool --user admin1 
--passwordfile pwordfile sampleConnectionPool


Resource Injection does not work in HandlerChain (6750245)


Resouce Injection does not work in HandlerChain due to EJB initialization order.


No known solution.

High Availability

This section describes known high availability database (HADB) issues and associated solutions.

Load balancer plugin healthcheck generates a large number of connection/disconnection at the background (load) (6453946)


Load balancer plug-in healthcheck generates a large number of connection/disconnection at the background (load). For health check purposes, a runDaemonMonitor thread performs connect/disconnect for every Application Server listener. This can lead to connection saturation on Enterprise Server.


A new attribute, monitor-interval-in-seconds, has been developed for the loadbalancer.xml file. This attribute can be used to insert a pause between connect/disconnect events in the case where hundreds of listeners are configure for the load balancer plug-in. Default pause value is 0.

HADB Configuration with Double Networks (no ID)

HADB configured with double networks on two subnets works properly on Solaris SPARC. However, due to problems in the operating system or network drivers on some hardware platforms, it has been observed that Solaris x86 and Linux platforms do not always handle double networks properly. This causes the following problems with HADB:

HADB Database Creation Fails (no ID)


Creating a new database may fail with the following error, stating that too few shared memory segments are available:

HADB-E-21054: System resource is unavailable: HADB-S-05512: Attaching shared memory segment with key "xxxxx" failed, OS status=24 OS error message: Too many open files.


Verify that shared memory is configured and the configuration is working. In particular, on Solaris 8, inspect the file /etc/system, and check that the value of the variable shmsys:shminfo_shmseg is at least six times the number of nodes per host.

hadbm set does not check resource availability (disk and memory space) (5091280)


When increasing device or buffer sizes using hadbm set, the management system checks resource availability when creating databases or adding nodes, but does not check if there are sufficient resources available when device or main-memory buffer sizes are changed.


Verify that there is enough free disk/memory space on all hosts before increasing any of the devicesize or buffersize configuration attributes.

Heterogeneous paths for packagepath not supported (5091349)


It is not possible to register the same software package with the same name with different locations at different hosts; for example:

hadbm registerpackage test --packagepath=/var/install1 --hosts europa11
Package successfully registered.
hadbm registerpackage test --packagepath=/var/install2 --hosts europa12
hadbm:Error 22171: A software package has already been registered with 
the package name test.


HADB does not support heterogeneous paths across nodes in a database cluster. Make sure that the HADB server installation directory (--packagepath) is the same across all participating hosts.

hadbm createdomain may fail (6173886, 6253132)


If running the management agent on a host with multiple network interfaces, the createdomain command may fail if not all network interfaces are on the same subnet:

hadbm:Error 22020: The management agents could not establish a 
domain, please check that the hosts can communicate with UDP multicast.

The management agents will (if not configured otherwise) use the "first" interface for UDP multicasts ("first" as defined by the result from


The best solution is to tell the management agent which subnet to use (set ma.server.mainternal.interfaces in the configuration file, e.g., ma.server.mainternal.interfaces= Alternatively one may configure the router between the subnets to route multicast packets (the management agent uses multicast address

Before retrying with a new configuration of the management agents, you may have to clean up the management agent repository. Stop all agents in the domain, and delete all files and directories in the repository directory (identified by repository.dr.path in the management agent configuration file). This must be done on all hosts before restarting the agents with a new configuration file.

Starting, stopping, and reconfiguring HADB may fail or hang (6230792, 6230415)


On Solaris 10 Opteron, starting, stopping or reconfiguring HADB using the hadbm command may fail or hang with one of the following errors:

hadbm:Error 22009: The command issued had no progress in the last 
300 seconds.
HADB-E-21070: The operation did not complete within the time limit, 
but has not been cancelled and may complete at a later time.

This may happen if there are inconsistencies reading/writing to a file (nomandevice) which the clu_noman_srv process uses. This problem can be detected by looking for the following messages in the HADB history files:

n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Child process noman3 733 
does not respond.
n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Have not heard from it in 
104.537454 sec.
n:3 NSUP INF 2005-02-11 18:00:33.844 p:731 Child process noman3 733 
did not start.


The following workaround is unverified, as the problem has not been reproduced manually. However, running this command for the affected node should solve the problem.

hadbm restartnode --level=clear nodeno dbname

Note that all devices for the node will be reinitialized. You may have to stop the node before reinitializing it.

The management agent terminates with the exception "IPV6_MULTICAST_IF failed" (6232140)


When starting on a host running Solaris 8 with several NIC cards installed, if there is a mixture of cards with IPv6 and IPv4 enabled, the management agent may terminate with the exception "IPV6_MULTICAST_IF failed."


Set the environment variable JAVA_OPTIONS to; for example:

export JAVA_OPTIONS=""

Alternatively, use Solaris 9 or later, which do not exhibit this problem.

clu_trans_srv cannot be interrupted (6249685)


There is a bug in the 64-bit version of Red Hat Enterprise Linux 3.0 that makes the clu_trans_srv process end up in an uninterruptible mode when performing asynchronous I/O. This means that kill -9 does not work and the operating system must be rebooted.


Use a 32-bit version of Red Hat Enterprise Linux 3.0.

hadbm does not support passwords containing capital letters (6262824)


Capital letters in passwords are converted to lowercase when the password is stored in hadb.


Do not use passwords containing capital letters.

Downgrading from HADB Version to HADB Version causes ma to fail with different error codes (6265419)


When downgrading to a previous HADB version, the management agent may fail with different error codes.


It is possible to downgrade the HADB database, however the management agent cannot be downgraded if there changes have been made in the repository objects. After a downgrade, you must keep use the management agent from the latest HADB version.

Install/removal and symlink preservation (6271063)


Regarding install/removal of HADB c package (Solaris: SUNWhadbc, Linux: sun-hadb-c) version <m.n.u-p>, the symlink /opt/SUNWhadb/<m> is never touched once it exists. Thus, it is possible that an orphaned symlink will exist.


Delete the symlink before install or after uninstall unless in use.

Management agents in global and local zones may interfere (6273681)


On Solaris 10, stopping a management agent by using the ma-initd script in a global zone stops the management agent in the local zone as well.


Do not install the management agent both in the global and local zone.

hadbm/ma should give a better error message when a session object has timed out and deleted at MA (6275103)


Sometimes, a resource contention problem on the server may cause a management client to become disconnected, When reconnecting, a misleading error message "hadbm:Error 22184: A password is required to connect to the management agent" may be returned.


Sometimes, a resource contention problem on the server may cause a management client to become disconnected, When reconnecting, a misleading error message "hadbm:Error 22184: A password is required to connect to the management agent" may be returned.

Check if there is a resource problem on the server, take proper action (e.g., add more resources), and retry the operation.

Non-root users cannot manage HADB (6275319)


Installing with Java Enterprise System (as root) does not permit non-root users to manage HADB.


Always login as root to manage HADB.

The Management Agent should not use special-use interfaces (6293912)


Special use interfaces with IP addresses like should not be registered as valid interfaces to be used for HADB nodes in the Management Agent. Registering such interfaces may cause problems if HADB nodes are set up on these interfaces by means of a user issuing a hadbm create command using host names instead of IP addresses. The nodes will then be unable to communicate, causing the create command to hang.


When using hadbm create on hosts with multiple interfaces, always specify the IP addresses explicitly using DDN notation.

Reassembly failures on Windows (6291562)


On the Windows platform, with certain configurations and loads, there may be a large number of reassembly failures in the operating system. The problem has been seen with configurations of more than twenty nodes when running several table scans (select *) in parallel. The symptoms may be that transactions abort frequently, repair or recovery may take a long time to complete, and there may be frequent timeouts in various parts of the system.


To fix the problem, the Windows registry variable HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters can be set to a value higher than the default 100. It is recommended that you increase this value to 0x1000 (4096). For more information, see. article 811003 from the Microsoft support pages.

Session state not maintained if the browser has another cookie with / path (6553415)


Cookies with a path equal to “/” interfere with the cookies of a highly available web application deployed at a context root other than “/” that uses in-memory replication as its persistence type, making it impossible for the highly available web application to maintain any HTTP session state. One common scenario where this may happen is when using the same browser to access both the Admin GUI (which is deployed at “/”) and the highly available web application.


Access the web application deployed at “/” from a different browser.

LB does not work with IIS 6; SASL32.DLL and ZLIB.DLL missing under as-install/lib (6572184)


SASL32.DLL and ZLIB.DLL are required files for Load Balancer to work with Windows IIS 6. These files are currently not available under as-install/lib.


Copy the two DLL files manually to as-install/lib. These files can be downloaded from:

Where OS represents the desired platform, and can be one of the following values:

DAS creation/startup and HA package propagation issues in Global Zone (6573511)


Two issues arise when installing or uninstalling Enterprise Server with High Availability packages in a Global Zone:

  1. HA packages get installed in all zones, which may not be desirable.

  2. When uninstalling, HA, MQ, JDK packages get removed from all zones, which may not be desirable.

This problem does not occur when installing or uninstalling from a root local zone.


Perform installation and uninstallations from a local root zone rather than a global zone.

Highly available webapps deployed at “/” unable to resume in-memory replicated HTTP sessions (Issue Tracker 2972)


Highly available web applications deployed at “/” are unable to maintain any HTTP sessions when using in-memory replication as their persistence type.


Deploy highly available web applications that use in-memory replication as their persistence type to a context root other than “/”. If you want to make such a web application available at “/”, you may designate it as the default-web-module of the virtual server to which the web application has been deployed.

AS LB installer did not put /usr/lib/mps path in apachectl LD_LIBRARY_PATH, can not start Apache SSL (6591878)


During Enterprise Server Load Balancer installation for Apache on Solaris, the installer updates LD_LIBRARY_PATH in the apachectl script. However, the installer does not correctly write the /usr/lib/mps path. On Solaris, the Apache security instance will not start without this path in LD_LIBRARY_PATH.


This issue exists only on Solaris platforms. To work around the issue, add /opt/SUNWappserver/appserver/lib/lbplugin/lib to your LD_LIBRARY_PATH.

Enable/disable LB for an instance/cluster should show correct status (6595113)


The Enable LoadBalance button is always enabled on the Clustered/Instance general page, regardless of what is saved in domain.xml.


AS9.1 EE IFR b58f/JES5 UR1. Cannot install Registry Server, because “incomplete” HA was detected. (6602508)


(Solaris only) After installing Enterprise Server 2.1 on SPARC Solaris 10 with HADB, you may receive the following error after starting Enterprise Server and then attempting to install JES 5 UR1 with Registry Server:

Dependency Error:  Installation can not proceed because the version of HA
Session Store 4.4.3 detected on this host is incomplete , and a compatible
version is required by Servervice Registry Deployment Support.


It is not possible to install Registry Server from JES 5 UR1 with Enterprise Server 2.1 IFR on Solaris machines. The Registry Server packages have to be installed manually using the pkgadd command from the following JES5 UR1 distribution directory:


Internet Explorer 6.0/7.0 browser specific: Exporting load balancer configuration file throws error (6516068)


(Internet Explorer 6 and 7 only) When attempting to export the Load Balancer configuration file (loadbalancer.xml) from Internet Explorer 6 or 7, the browser displays an error message saying that the sun-loadbalancer_1_2.dtd DTD file cannot be located.


To save the file, use the following workaround:

  1. Click Export on the Load Balancer page in Internet Explorer.

    The “XML page cannot be displayed” message is displayed.

  2. Click the error frame, and then choose File->Save As from the Internet Explorer.

  3. Save the loadbalancer.xml file to the directory of your choice.


This section describes known installation issues and associated solutions.

The start-domain Command Times Out on OpenSolaris 2008.11 (6820169 and 6741572)


On OpenSolaris 2008.11, when you attempt to start the domain with the asadmin start-domain command, the following error message is displayed:

Timeout waiting for domain domain1 to go to starting state.
CLI156 Could not start the domain domain1.


The domain has started successfully. Correct the time and date after rebooting the machine.

Installation with 64–bit JDK Fails (6796171)


Installation fails on 64–bit systems that have 64–bit JDK because the installer tries to use the 64–bit JDK.


If you are installing Sun GlassFish Enterprise Server on a 64–bit system, download the 32–bit JDK and use it to install Sun GlassFish Enterprise Server on your 64–bit machine. You will need to use the following command: ./distribution_filename —javahome path to 32–bit JDK location

After installation, to ensure that Sun GlassFish Enterprise Server uses a 64–bit JDK, edit the value of the AS_JAVA variable in the asenv.conf file to point to the 64–bit JDK installation.

Enterprise Server installer crashes on Linux (6739013)


This problem has been observed on systems running Linux with the environment variable, MALLOC_CHECK_, set to 2.


Set the environment variable, MALLOC_CHECK_ to 0. Run one of the following commands:

Installation shutdown hanging on some Linux systems after clicking the "Finish" button (5009728)


This problem has been observed on several Linux systems. It is most common on Java Desktop System 2 but has also been observed on Linux Red Hat distributions.

After clicking the "Finish" button on the last installer screen, the installer fails to launch a browser window containing the product About page or product registration page, and hangs indefinitely, not returning the command prompt.


Exit the installer by pressing Ctrl+C in the terminal window in which the installer was started. After doing this, browser window containing product About page or registration page will sometimes be launched, but if it does not show up, start the browser and enter following URL in order to review About page:


If you also selected the installation option to register the product, follow the link to registration page available on product About page.

On Windows, the imq directory needs to be created during installation (6199697)


On Windows, immediately after installation, the Message Queue broker fails on startup with a message saying the directory drive:\as\domains\domain1\imq does not exist.

Note that if the broker is started after starting domain1, the directory will be created by the Application Server and the problem will not occur.


  1. Create the var_home_dir_location before creating the broker:

    $imqbrokerd -varhome var_home_dir_location

    For example:

    $imqbrokerd -varhome D:\as\domains\domain1\imq

Uninstall does not update productregistry file properly; unable to use silent mode to install (6571598)


If the Enterprise Server productregistry file contains shared component configurations, an Enterprise Server uninstallation procedure does not update the productregistry file correctly, and you will not be able to use silent mode in a subsequent installation unless the productregistry file is renamed or removed. Leaving the shared components entries in the productregistry file intact is by design, but it leads to confusion with subsequent silent installs.


After a successful uninstallation is reported back through uninstall log files, delete the productregistry file prior to running a subsequent installation. To verify that a previous uninstallation has completed successfully, look for a appserv_uninstall.class file in as-install. This file will not be present if the uninstallation was successful.

Note –

Do not delete the productregistry if the uninstallation was not successful.

The productregistry file is located in /var/sadm/install on Solaris and /var/tmp on Linux.

IFR. Was not able to install AS in the sparse local zone, MQ packages issue. (6555578)


When installing Enterprise Server in a sparse local zone, the installation fails if Message Queue (MQ) is not installed first. The installer attempts to install MQ, and then the whole installation fails.


MQ must be manually installed in the global zone before installing Enterprise Server in a sparse local zone. There are two work-arounds for this issue:

  1. Install MQ 4.1 manually in the global zone from the same media on which Enterprise Server 2.1 IFR installation is located to get the latest MQ packages.

    1. Use the installer that corresponds to your platform:
    2. Unzip the bits and run the installer.

      The installer will be in the mq4_1-installer directory.

  2. Install any component of IFR installation in global zone. This action would check the version of MQ in GZ and if required upgrade it to the one bundled in Enterprise Server 2.1 IFR. Even Selecting and Installing the Sample Applications component upgrades MQ to IFR version.

    1. Run the Enterprise Server installation in the global zone, but select only the sample components.

      The sample component installation also installs MQ and Enterprise Server shared components in all zones.

    2. Run the Enterprise Server installation again, this time in the local sparse zone.

      Installation should complete without any problems.

IFR Installation -console prompt has to be removed: “Do you want to upgrade from previous Application?” (6592454)


When running the Enterprise Server 2.1 IFR installer with the —console option (command-line mode), you are prompted:

Do you want to upgrade from previous Application Server version?

Unfortunately, the IFR installer does not support such upgrades, and so this prompt is erroneous. If you answer yes to the prompt, the installation proceeds normally, but no indication that a complete installation was performed, rather than an upgrade.


Use the upgrade tool if you want to upgrade your Enterprise Server installation.

After upgrade, the following exceptions are seen in the log when a domain is started. (6774663)


The following exceptions might be thrown:

#|2008-11-19T01:44:37.422+0530|SEVERE|sun-appserver9.1|org.apache.catalina.session.ManagerBase|_ThreadID=17;_ThreadName=pool-1-thread-3;_Req uestID=cc0ddf54-a42e-400a-9788-e30d79a25d88;|PWC2768: IOException while loading persisted sessions: org.apache .catalina.session.StandardSession; local class incompatible: stream classdesc serialVersionUID = 8647852380089530442, local class serialVersi onUID = -8515037662877107054 org.apache.catalina.session.StandardSession; local class incompatible: stream classdesc serialVersionUID = 864 7852380089530442, local class serialVersionUID = -8515037662877107054..... .....


After upgrade is done and the upgrade domain is started, these exceptions can be ignored if they occur.

Java EE Tutorial

When using the Administration Console to create any resource, use the Targets tab to specify the server as the target. If you use the command line or an asant target, the server is the default target, no further action is required.

Java Persistence

TopLink expects my Collection field/property to be cloneable (Issue Tracker 556)


If the java.util.Arrays.asList() API is used to convert an Object[] to Collection, the JDK returns an implementation of java.util.ArrayList that is not cloneable. This results in the following exception:

The method invocation of the method [protected native java.lang.Object 
java.lang.Object.clone() throws java.lang.CloneNotSupportedException] on the object 
[[pkg.A id = xxx]], of class [class java.util.Arrays$ArrayList], triggered an 
exception. Internal Exception: java.lang.reflect.InvocationTargetException Target 
Invocation Exception: java.lang.CloneNotSupportedException: 

This issue is tracked at


Create another collection using its constructor; for example:

myCollection = new ArrayList(java.util.Arrays.asList(a))

GenerationType.IDENTITY and DataDirect Driver with SyBase (Issue Tracker 2431)


An attempt to insert an entity that uses GenerationType.IDENTITY fails when the DataDirect driver is used with SyBase. The attempt fails because the DataDirect driver creates a stored procedure for every parameterized prepared statement.


In the domain.xml file, set the property PrepareMethod=direct on the corresponding data source.

Lifecycle Management

This section describes known lifecycle management issues and associated solutions.

Setting ejb-timer-service property causes set command to fail (6193449)


After setting the ejb-timer-service property minimum-delivery-interval to 9000, an attempt to set the ejb-timer-service property redelivery-interval-in-mills to 7000 causes the set command to fail with the following error:

[echo] Doing admin task set
[exec] [Attribute(id=redelivery-interval-internal-in-millis) : 
Redelivery-Interval (7,000) 
should be greater than or equal to Minimum-delivery-interval-
in-millis (9,000)]
[exec] CLI137 Command set failed.

The problem is that the logic that relates the redelivery interval property to the minimum delivery property is incorrect and prevents you from using the GUI or the CLI to set any value where the minimum delivery interval is greater than redelivery interval.

The minimum-delivery-interval-in-millis must always be set equal to or higher than ejb-timer-service property redelivery-interval-in-millis. The problem is that there is an erroneous validation check in the aerver to verify that the value for redelivery-interval-in-millis is greater than the value for minimum-delivery-interval-in-millis.


Use the default values for these properties, as follows:


Values other than these defaults will generate an error.

Error thrown when list JMS physical destinations within non-DAS config (6532532)


If you are trying to view the JMS Physical Destinations using the default-config, you will see an error message.


This is expected behavior. In Enterprise Server 2.1, default-config is a template of configuration information and hence JMS operations (such as list and create) cannot be executed for the default-config. These JMS operations can, however, be executed for the configurations of your cluster or standalone instances.

Win2003 only: Non-paged pool leak memory, breaking tcp stack and richaccess test (6575349)


(Windows 2003 only) There are memory leaks on Windows 2003 systems when performing rich access functions. The problem occurs because the Win32 nonpaged pool keeps growing, eventually bringing down the entire TCP/IP stack. Once the failure happens, the TCP/IP stack is left in an recoverable state, and the only way restore it is by rebooting the Windows 2003 system.


There are two workarounds to this issue:


This section describes known logging issues and solutions.

Setting debug statement for access,failure causes hang in server startup (6180095)


Setting the option for the JVM will cause the server instance startup to freeze with a deadlock; for example, setting the following in domain.xml causes the problem:



None at this time. Please avoid setting this flag.

Message Queue

This section describes known Java message queue issues and associated solutions.

Enterprise Server Does Not Start If MQ Broker is Not Started (6740797)


If you configure JMS to be REMOTE, Enterprise Server fails to start if the MQ broker is not started.


Set the following JVM option as follows: com.sun.enterprise.jms.CONNECT_MQ_LAZILY=true. After setting this JVM option, you can start Enterprise Server if the MQ broker is not started. However, it is recommended that you start MQ before starting the server.

JMS reconnection does not successfully complete in certain cases that are timing dependent (6173308, 6189645, 6198481, 6199510, 6208728)


Failures to reconnect in timing-dependent scenarios can be caused by several problems.


You can work around these problems by:

MQ broker fails to start with cluster profile on Linux (6524871)


After creating a domain with a cluster profile on a Linux system, you may encounter a java.lang.OutOfMemoryError: Java heap space error, and the server instance may fail to restart because the MQ broker does not start. The system never recovers after this condition. The problem is a misconfigured /etc/hosts file; specifically, the server host name is pointing to the loopback address


By design, an MQ broker cluster cannot start with the network device configured to point to the loopback address. This is not a bug. The solution is to make sure that the /etc/hosts file for the Enterprise Server host does not point to

Mismatch of old and new classes is created when imqjmsra.jar is loaded before upgrade (6740794)


During server startup, the server checks the Message Queue version. If the Message Queue version is incorrect, then the server upgrades using the imqjmsra.jar. This upgrade JAR and its classes will not be available to the server until the next restart. This situation only occurs if Message Queue is upgraded alone, or if Application Server is patched alone. A side effect of this situation is that sometimes server does not start.


Both Message Queue and Enterprise Server need to be maintained at the same patch level, or restart the server.


This section describes known monitoring issues and associated solutions.

Some of the HTTP Service monitoring statistics do not present useful information and should be ignored (6174518)


When viewing the monitoring statistics of some elements of the HTTP Service, some values presented do not correspond to current values or are always 0. Specifically, the following HTTP Service statistics do not present information applicable to the Enterprise Server, and should be ignored:


These monitors will be removed in future releases and replaced with more appropriate information.

Open JNDI Browsing from Admin UI dumps a huge amount of exceptions in the server.log (6591734)


Many exceptions are thrown when the JNDI browser is opened from the Admin GUI.


None at this time.


This section describes known issues and associated solutions related to the packaging of the software code for the Enterprise Server 2.1 product.

AIX: monitor command doesn't work on AIX (6655731)


The monitor command cannot be run on the AIX operating system because the library file is not packaged in Enterprise Server 2.1.

ProcedureSolution: To Install the Missing Library File

  1. Download the JAR file from.

  2. Change to the directory to where you downloaded the appserv-native-9.1.1-b16a.jar file.

    prompt% cd destination-dir
  3. Extract the contents of the appserv-native-9.1.1-b16a.jar file.

    prompt% jar xf appserv-native-9.1.1-b16a.jar
  4. Copy the file to the as-install/lib directory.

    prompt% cp as-install/lib


This section describes known issues and associated solutions related to the sample code included with the Enterprise Server 2.1 product.

After upgrade Enterprise Server samples and JES5 portal samples compete on derby port 1527 (6574563)


On Windows, after upgrading to Enterprise Server 2.1, the samples and JES5 portal samples compete on Derby port 1527. Specifically, Enterprise Server 2.1 automatically starts JavaDB on port with APP:APP, however the JES5 Portal JavaDB wants to bind to hostnameIP:1527 with portal:portal.

This bug describes an issue that was already seen for JES 5, Bug 6472173. The workaround for bug 6472173 is documented in the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows on


Start the Derby database using the following command:

JES-installation-dir\appserver\bin\asadmin start-database --dbhome JES-installation-dir\portal\data\derby


This section describes known issues and associated solutions related to Enterprise Server and web application security and certificates.

OutofMemory Error in SSL Scenarios During Heavy Stress (JDK 6 Issue 23)


A JDK bug (See: in JDK6 Sun PKCS11 Provider could cause an OutOfMemoryError when running certain SSL scenarios under heavy stress.


If you run into this issue, remove provider from the file in your JRE installation.

AIX: WSS dynamic encrypt key test failed due to server side certification validation error (6627379)


On the AIX platform, dynamic encryption for the determination of an encryption key for a response is failing. The failure occurs during the validation of the certificate on the server side.

In response to the failure, the following error messages are written to the server's log file server.log:

Unable to validate certificate

Error occurred while resolving key information
com.sun.xml.wss.impl.WssSoapFaultException: Certificate validation failed


Install Metro 1.1 on Enterprise Server 2.1

AIX: @RunAs at EJB module authorization test failed AccessLocalException: Client not authorized (6627385)


A method in an enterprise bean whose run-as, or propagated, security identity is defined by using the @RunAs annotation attempts to invoke a method in another enterprise bean. If no run-as principal is defined in the sun-ejb-jar.xml deployment descriptor file, the attempt might fail with a javax.ejb.AccessLocalException exception.

javax.ejb.AccessLocalException: Client not authorized for this invocation.


In the sun-ejb-jar.xml deployment descriptor file, define in the principal-name element the principal name for which the run-as role specified.

SSL termination is not working (6269102)


SSL termination is not working; when Load Balancer (Hardware) is configured for SSL termination, the Enterprise Server changes the protocol from https to http during redirection.


Add a software load balancer between the hardware load balancer and the Enterprise Server.

Socket connection leak with SSL (6492477)


Because of a JVM bug, there is a leak issue with some JDK versions when security-enabled is set to true on an HTTP listener. Specifically, the steps to reproduce this bug are as follows:

  1. Set security-enabled to true on the HTTP listener:

    <http-listener acceptor-threads="1" address="" 
    blocking-enabled="false" default-virtual-server="server" enabled="true" 
    family="inet" id=" http-listener-1" port="8080" security-enabled="true" 
    server-name="" xpowered-by="true">
  2. Comment out stopping domain at the end of quicklook tests.

  3. Run quicklook tests.

  4. Check socket usage:

    netstat -an | grep 8080

    The following are shown to be in use:

    *.8080               *.*                0      0 49152      0 LISTEN
    *.8080               *.*                0      0 49152      0 BOUND

This issue is tracked on the GlassFish site at


Upgrade to the latest JDK version.


This section describes known upgrade issues and associated solutions.

On some Linux systems, the installer running "Upgrade in place" fails to start upgrade tool after clicking on the "Start Upgrade Wizard" button (6207337)


This problem has been observed on several Linux systems, it is most common on Java Desktop System 2 but has also been observed on Red Hat distributions.

After clicking the "Start Upgrade Tool" button on the final installer screen, the installer fails to launch the upgrade tool to complete the upgrade process, and hangs indefinitely, not returning the command prompt.


This issue is not encountered if command line installation mode is used to run upgrade in place.

  1. If you ran upgrade in place in GUI mode and encountered this problem, exit the installer by pressing Ctrl+C in the terminal window in which the installer was started.

  2. Start upgrade tool from the terminal window, using following command:

    as-install/bin/asupgrade --source as-install/domains --target 
    as-install --adminuser adminuser --adminpassword adminpassword 
    --masterpassword changeit

    adminuser and adminpassword should match the values used for the installation you are upgrading.

  3. When the upgrade tool completes the upgrade process you can also start the browser and enter following URL in order to review About page:


If you also selected the installation option to register the product, follow the link to registration page available on product About page.

Self-signed certificate is not trusted during and after upgrade from 8.0 Platform Edition (PE) to 8.1 Enterprise Edition (EE) UR2 (6296105)


Remove the following entries from the target domain.xml (after the upgrade) and restart the server:


(sbs-manual, sbs-installer) throws Server Instance server does not have a system connector named null (6545145)


When upgrading from Enterprise Server 8.0PE to 2.1, an error is thrown saying the server does not have system connector named null, and invalid user information as seen in sbs-manual. Even after changing the hardcoded values, the same error message is seen.


You can only encounter this bug while upgrading from a 8.0 PE toEnterprise Server. The workaround is to upgrade to either 8.1, 8.2, or 9.0 and then upgrade to Enterprise Server.

Different domains are lost during upgrade when different build combinations are used (6546130)


When performing an inplace upgrade, in cases where there are multiple domains in the source, the installer invokes upgrade tool even though the process is killed. This happens when it is invoked in GUI mode.


  1. Install inplace in the CLI mode, and exit when the installer prompts you to select the upgrade tool at the end of installation process. This does not delete any of the domains present in the domains directory. Upgrade tool should be manually invoked from the bin directory.

  2. When installing inplace in GUI mode, make a backup of the domains present in the domains root to prevent losing any domains in the process. At the end of the installation process, exit when the installer prompts you to invoke the upgrade tool. Copy any backed up domains into the domains directory if they have been lost. Launch upgrade tool manually to do an upgrade.

Solaris: pre-filled Master password in upgrade Tool is from Enterprise Server 2.1 and not from AS8.2 (6565825)


When upgrading from AS 8.2, the master password from the 8.2 installation is not inherited in the target installation. This subsequently causes an authentication error at the next admin login.


The default admin password in Enterprise Server 2.1 is changeit. To avoid problems when logging in to the Enterprise Server after upgrading from 8.2, do one of the three following things:

Localized Online Help for asupgrade GUI Does Not Exist (6610170)


When running the asupgrade GUI in a language other than English, the online help for the GUI is not localized for the selected non-English language.


None at the time. Online help is scheduled to be localized in all non-English target languages.

Upgrade Tool deleted nodeagents directory when upgrade (reverse order) with multiple domains (6636871)


After a side-by-side upgrade of a configuration that contains multiple domains, only the node agents of the last processed domain are present. This issue occurs because Upgrade Tool removes and re-creates the nodeagents directory in the target each time Upgrade Tool processes a domain.

ProcedureSolution: To Preserve All Node Agents in a Side-by-Side Upgrade of Multiple Domains

  1. After processing each domain, create a zip file of the nodeagents directory.

  2. When all domains have been processed, unzip the files that you created.

    All node agents should now be present.

In-place upgrade does not update the index.html file of existing domain (6831429)


While performing in-place upgrade, the index.html file of a domain that already exists is not replaced. It might still show the old version of the server. This index.html file could be replaced by the index.html file from SGES_BASE.

SGES_BASE/lib/install/templates/ee/index.html DOMAIN_DIR/docroot/index.html

Web Container

This section describes known web container issues and associated solutions.

On Windows, deploying an application using --precompilejsp=true can lock JAR files in the application, causing later undeployment or redeployment to fail (5004315)


If you request precompilation of JSPs when you deploy an application on Windows, later attempts to undeploy that application or to redeploy it (or any application with the same module ID) will not work as expected. The problem is that JSP precompilation opens JAR files in your application but does not close them, and Windows prevents the undeployment from deleting those files or the redeployment from overwriting them.

Note that undeployment succeeds to a point, in that the application is logically removed from the Application Server. Also note that no error message is returned by the asadmin utility, but the application's directory and the locked jar files remain on the server. The server's log file will contain messages describing the failure to delete the files and the application's directory.

Attempts to redeploy the application after undeploying fail because the server tries to remove the existing files and directory, and these attempts also fail. This can happen if you try to deploy any application that uses the same module ID as the originally deployed application, because the server uses the module ID in choosing a directory name to hold the application's files.

Attempts to redeploy the application without undeploying it first will fail for the same reasons.


If you attempt to redeploy the application or deploy it after undeploying it, the asadmin utility returns an error similar to the one below.

An exception occurred while running the command. The exception 
message is: CLI171 Command deploy failed : Deploying application in 
domain failed; Cannot deploy. Module directory is locked and can't 
be deleted.


If you specify --precompilejsps=false (the default setting) when you deploy an application, then this problem will not occur. Be aware that the first use of the application will trigger the JSP compilation, so the response time to the first request will be longer than for later requests.

Note also that if you do precompile, you should stop and restart the server before undeploying or redeploying the application. The shutdown frees the locked JAR files so the undeployment or redeployment after the restart can succeed.

Unable to deploy WAR with Servlet 2.4-based web.xml that contains an empty <load-on-startup> element (6172006)


The optional load-on-startup servlet element in a web.xml indicates that the associated servlet is to be loaded and initialized as part of the startup of the web application that declares it.

The optional content of this element is an integer indicating the order in which the servlet is to be loaded and initialized with respect to the web application's other servlets. An empty <load-on-startup> indicates that the order is irrelevant, as long as the servlet is loaded and initialized during the startup of its containing web application.

The Servlet 2.4 schema for web.xml no longer supports an empty <load-on-startup>, meaning that an integer must be specified when using a Servlet 2.4 based web.xml. If specifying an empty <load-on-startup>, as in <load-on-startup/>, the web.xml will fail validation against the Servlet 2.4 schema for web.xml, causing deployment of the web application to fail.

Backwards compatibility issue. Specifying an empty <load-on-startup> still works with Servlet 2.3 based web.xml.


Specify <load-on-startup>0</load-on-startup> when using a Servlet 2.4 based web.xml to indicate that servlet load order does not matter.

Unable to compile JSP page on resource constrained servers (6184122)


The JSP page is accessed but fails to compile, and the server log contains the error message "Unable to execute command" with the following stack trace:

exec( at
at org.apache.jasper.compiler.Compiler.generateClass(


Set the JSP compilation switch "fork" to "false."

This can be done either of two ways:

Either setting will prevent ant from spawning a new process for javac compilation.

Enterprise Server does not support auth-passthrough Web Server 6.1 Add-On (6188932)


The Sun GlassFish Enterprise Server 2.1 adds support for the functionality provided by the auth-passthrough plugin function available with Sun GlassFish Enterprise Server Enterprise Edition 7.1. However, in Enterprise Server 2.1, the auth-passthrough plugin feature is configured differently.

The auth-passthrough plugin function in Enterprise Server Enterprise Edition 7.1 has been useful in two-tier deployment scenarios, where:

In such network architectures, a client connects to a front-end web server, which has been configured with the service-passthrough plugin function and forwards HTTP requests to the proxied Application Server instance for processing. The Application Server instance can only receive requests from the web server proxy, but never directly from any client hosts. As a result of this, any applications deployed on the proxied Application Server instance that query for client information, such as the client's IP address, will receive the proxy host IP, since that is the actual originating host of the relayed request.


In Application Server Enterprise Edition 7.1, the auth-passthrough plugin function could be configured on the proxied Application Server instance in order to make the remote client's information directly available to any applications deployed on it; as if the proxied Application Server instance had received the request directly, instead of via an intermediate web server running the service-passthrough plugin.

In Enterprise Server 2.1, the auth-passthrough feature may be enabled by setting the authPassthroughEnabled property of the <http-service> element in domain.xml to TRUE, as follows:

<property name="authPassthroughEnabled" value="true"/>

The same security considerations of the auth-passthrough plugin function in Application Server Enterprise Edition 7.1 also apply to the authPassthroughEnabled property in Enterprise Server 2.1. Since authPassthroughEnabled makes it possible to override information that may be used for authentication purposes (such as the IP address from which the request originated, or the SSL client certificate), it is essential that only trusted clients or servers be allowed to connect to an Enterprise Server 2.1 instance with authPassthroughEnabled set to TRUE. As a precautionary measure, it is recommended that only servers behind the corporate firewall should be configured with authPassthroughEnabled set to TRUE. A server that is accessible through the Internet must never be configured with authPassthroughEnabled set to TRUE.

Notice that in the scenario where a proxy web server has been configured with the service-passthrough plugin and forwards requests to an Enterprise Server instance with authPassthroughEnabled set to TRUE, SSL client authentication may be enabled on the web server proxy, and disabled on the proxied Enterprise Server instance. In this case, the proxied Enterprise Server instance will still treat the request as though it was authenticated via SSL, and provide the client's SSL certificate to any deployed applications requesting it.

Web Server

AS 9.1 b50e.Linux. Can not start WS after AS LB installation: open shared (6572654)


This issue only applies you are using the Sun GlassFish Web Server with Enterprise Server and Load Balancer on a Linux system. In such a case, after installing Enterprise Server and a load balancer, the Web Server may fail to start because and are in conflict. These libraries are present in both /opt/sun/private/lib and /opt/sun/appserver/lib.


The correct libraries to use are the ones in /opt/sun/appserver/lib because lbplugin is built against those libraries. Once you remove the two libraries from /opt/sun/private/lib, Web Server should start without error.

Alternatively, if you do not want to delete the libraries from /opt/sun/private/lib, you can instead put /opt/sun/appserver/lib before /opt/sun/private/lib in LD_LIBRARY_PATH in the Web Server startserv script; that is, replace:

# Add instance-specific information to LD_LIBRARY_PATH for Solaris and Linux
/opt/sun/appserver/lib:/opt/sun/appserver/lbplugin/lib"; export LD_LIBRARY_PATH 


# Add instance-specific information to LD_LIBRARY_PATH for Solaris and Linux

Web Services

This section describes known web container issues and associated solutions.

Ant task wsimport fails with Java EE SDK b33d (using JDK 1.6) with NoClassDefFoundError (6527842)


You may encounter a problem when running the JAX—WS tests with the JDK 1.6 included with the Java EE SDK b33d. The tests immediately abort with the following message:

[wsimport] Exception in thread "main" java.lang.NoClassDefFoundError: \

This error occurs even though the webservices-tools.jar does contain com/sun/tools/ws/WsImport.class, com/sun/tools/ws/ant/WsImport.class, and com/sun/tools/ws/ant/WsImport2.class. Moreover, the same test workspace works without problem using the 1.5.0-10 JDK.


Copy the webservices-api.jar to $JAVA_HOME/jre/lib/endorsed before running the JAX-WS tests.

publish-to-registry commands fail in IFR EE builds (6602046)


JAXR uses SAAJ to send soap messages to the registry. In the non-IFR case, the SAAJ impl classes are under lib/webservices-rt.jar. In the IFR case, the SAAJ classes are still under lib/webservices-rt.jar. In addition, saaj-impl.jar is located in the /usr/share/lib directory. This jar file is picked up by Enterprise Server and has precedence over classes from webservices-rt.jar. This jar file does not have the necessary security permissions to send soap messages to the Web services registry. The packaging should be modified to grant permissions to the jars under /usr/share/lib directory or not depend on the /usr/share/lib jars.


Add the following to the server.policy file:

grant codeBase "file:/usr/share/lib/saaj-impl.jar" {

wscompile fails with "package javax.xml.rpc does not exist" on JDK6 u4 b3 (6638567)


The wscompile ant task fails for JDK 6 Update 4. For each JAX-RPC API class, the following error message is displayed:

package package-name does not exist


Before running the wscompile ant task, ensure that javaee.jar is specified in the class path, not j2ee.jar.