Sun Java System Application Server 9.1 Release Notes

Chapter 3 Known Issues and Limitations

This chapter describes known problems and associated workarounds for the Sun Java System Application Server 9.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.

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


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

Cannot restore backed-up domain with another name (6196993)


Mirroring of a domain on the same Application Server installation cannot be performed using the backup-domain and restore-domain commands because the domain cannot be restored 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.


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.1 work only for backing up and restoring the same domain on the same machine.

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


J2SE 1.4.x, 5.0, or later can be configured on the Application 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 Application Server Virtual Machine. An undesirable side-effect of this is that the administration functions are affected adversely, and the Application Server 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 Application 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 Java System Application Server 9.1 Administration Guide.

On UNIX, overly restrictive execute permissions on Application Server start and stop scripts (6206176)


If you run the asadmin restore-domain command while logged in as user "A", the scripts will end up with permissions as 744 (rwxr--r--). If you subsequently attempt to start or stop a domain as user "B" (even if "B" is root), it will fail because the scripts are only executable for "A".


Change the permissions on the scripts:

chmod 755 appserv/domains/domain-name/bin/*

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.

Application Server restart using sun-appserv-admin causes LoginException error (6288893)


  1. Rename the existing <as_install>/bin/asant script to asant.bak.

  2. Copy the asant.template file in <as_install>/lib/install/templates/ee (for SE/EE version) to the <as_install>/bin/ directory and rename the file asant.

  3. Edit the newly copied <as_install>/bin/asant script, replacing the %CONFIG_HOME% token with <as_install>/config.

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

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


The .asadmintruststore file is not described in the Application 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 Application Server cluster instance is LOCAL. When Application 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 Application 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.

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

    $AS91_HOME/bin/asadmin.bat create-jms-host --port 5858 --user admin --passwordfile \
    $AS91_HOME/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.

    $AS91_HOME/bin/asadmin.bat set --port 5858 --user admin --passwordfile \
    $AS91_HOME/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 Application Server 9.1.

Default ports changing in each AS major release (6566481)


The default admin port has changed in each of the past three major Application 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 Application Server releases going forward will retain the default 4848 port.

On Windows: Application Server fails to start due to NSS initialization failure. (6618442)


In some cases, Application Server (enterprise profile) might not start on Windows when PKCS11 fails to initialize.


Remove softokn3.dll from the Windows system path.

Apache and Load Balancer Plugin

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

The High-Availability Administration Guide contains incorrect instructions for using openssl with Apache (6306784)

When compiling and building openssl, run the following commands:

cd openssl-0.9.7e



Also, for Apache 1.3, the directory name of the mod_ssl source will vary depending upon the release of Apache used. For example, for Apache 1.3.33, the name is mod_ssl-2.8.22-1.3.33.

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 Application Server 9.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 Java System Application Server 9.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 Java System Application Server 9.1 Administration Guide for instructions.

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


The bundled Java DB database is not automatically restarted after a host system or Solaris zone reboot, or an Application 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 Application Server instance.


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

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

Refer to Application Server Administration Tools in Sun Java System Application Server 9.1 Quick Start Guide in the Sun Java System Application Server 9.1 Quick Start Guide for more information about asadmin command options.


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:

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 the bundled ANT for things outside the Application Server is not recommended.

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.

High Availability

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

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.

createdomain may fail (6173886, 6253132)


If running the management agent on a host with multiple netwrok 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 <appserver-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 <appsrver-install>/lib.


Copy the two DLL files manually to <appserver-install>/lib. These files can be downloaded from:<OS>/aslb/jars/aslb-9.1-MS4-b5.jar

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 Application 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 Application 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. Can not install Registry Server, because “incomplete” HA was detected. (6602508)


(Solaris only) After installing Application Server 9.1 on SPARC Solaris 10 with HADB, you may receive the following error after starting Application 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 Application Server 9.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:


IE 6.0 browser specific: Exporting load balancer configuration file throws error (6516068)


(Internet Explorer 6 only) When attempting to export the Load Balancer configuration file (loadbalancer.xml) from Internet Explorer 6, 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.

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 installing Application Server Enterprise Edition, 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

Spurious warning while installing SDK on Windows Vista (6533646)


When installing the bundled SDK on Windows Vista, you may encounter the error “Unsupported Installation Platform Detected.” However, the installation suceeds without any issues.


This is not really a problem. Application Server runs on Windows Vista, and this erroneous message will be removed in future versions of the product.

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


If the Application Server productregistry file contains shared component configurations, an Application 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 <install_dir>. 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 Application 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 Application 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 Application Server 9.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 Application Server 9.1 IFR. Even Selecting and Installing the Sample Applications component upgrades MQ to IFR version.

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

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

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

      Installation should complete without any problems.

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


When running the Application Server 9.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 Application Server installation.

Java EE Tutorial

To run the Java EE 5 Tutorial on the Sun Java System Application Server 9.1 perform these tasks:

MDB failure in Java EE Tutorial example (6591307)


In Chapter 32, Java EE Examples Using the JMS API, in The Java EE 5 Tutorial, An Application Example That Consumes Messages from a Remote Server in The Java EE 5 Tutorial," this example no longer works. The MDB fails to receive the message. The other two examples that send messages between two systems still work correctly (Running JMS Client Programs on Multiple Systems in The Java EE 5 Tutorial and An Application Example That Deploys a Message-Driven Bean on Two Servers in The Java EE 5 Tutorial.


Will be fixed in a later Application Server build.

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))

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 Application Server 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 Application Server 9.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.

  1. Use Grizzly blocking mode by configuring the domain.xml http-listener attribute, blocking-enabled="true" or add the following http-listener property:

    <property name="blocking" value="true"/>
  2. Use Windows Vista or Windows XP.


This section describes known logging issues and solutions.

Setting debug statement for access,failure causes hang in Application 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.

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 Application Server host does not point to


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 Application 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 and associated solutions related to the sample code included with the Application Server 9.1 product.

Documentation does not explicitly state that you need to create JMS resources Documentation does not explicitly state that you need to create JMS resources (6198003)


Documentation does not explicitly state that you need to create JMS resources before running the MQ Failover Sample Application following the asadmin deploy instructions.

The error thrown is as follows:

/opt/SUNWappserver/domains/domain1/config/sun-acc.xml -name 
MQFailoverTestClient -textauth -user j2ee -password j2ee
Nov 18, 2004 10:50:17 PM com.sun.enterprise.naming.NamingManagerImpl 
SEVERE: NAM0006: JMS Destination object not found: jms/durable/TopicA
Nov 18, 2004 10:50:18 PM com.sun.enterprise.naming.NamingManagerImpl 
SEVERE: javax.naming.NameNotFoundException

The documentation does not explicitly state that JMS resources must be manually created if manual deployment is done using asadmin deploy commands, and that the provided ant targets to deploy the sample application should be used.


Use the asant deploy target for the build.xml script, which creates the required JMS resources to run the application.

On Linux, a runtime error is displayed during certificate creation in web services/security samples (6198239)


When deploying the install_dir/samples/webservices/security sample (basicSSl) on Linux, the certificate is not created and an error similar to the following is thrown:

generate_certs: [echo] ***Exporting certificate from NSS database 
[exec] Result: 1 [echo] ***Generating Java Keystore from generated 
certificate [exec] keytool error: java.lang.Exception: Input not an 
X.509 certificate [exec] Result: 1 [echo] ***Generating Java trust 
store from generated certificate [exec] keytool error: java.lang.
Exception: Input not an X.509 certificate [exec] Result: 1
generate_certs: [echo] ***Exporting server certificate from NSS database to 
a PKCS12 certificate file [exec] /opt/sun/appserver/lib/pk12util: /usr/lib/ version `NSS_3.9' not found (required by /opt/sun/appserver/lib/
pk12util) [exec] /opt/sun/appserver/lib/pk12util: /usr/lib/ 
version `NSS_3.6' not found (required by /opt/sun/appserver/lib/pk12util) 
[exec] /opt/sun/appserver/lib/pk12util: /usr/lib/ version 
`NSS_3.7' not found (required by /opt/sun/appserver/lib/pk12util) [exec] 
Result: 1

The problem is that NSS libraries are in different locations on Linux installations than on Solaris installations. You need to make sure that the LD_LIBRARY_PATH points to the proper NSS libraries when deploying on Linux. Either set LD_LIBRARY_PATH in your environment, or set it in the install_dir/bin/asant shell wrapper script.


Do one of the following:

After upgrade AS9.1 samples and JES5 portal samples compete on derby port 1527 (6574563)


On Windows, after upgrading to Application Server 9.1, the samples and JES5 portal samples compete on Derby port 1527. Specifically, Application Server 9.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.


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 Application Server and web application security and certificates.

SSL termination is not working (6269102)


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


Add a software load balancer between the hardware load balancer and the Application 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.

Upgrade Utility

This section describes known Upgrade utility issues and associated solutions.

Domains created in custom-path other than install_dir/domains directory are not upgraded directly (6165528)


Domains created in custom-path other than install_dir/domains directory are not upgraded directly while upgrading from Application Server Enterprise Edition 8 to Application Server Enterprise Edition 8.1.

When running the Upgrade Utility and identifying the install_dir as the source installation directory, the upgrade process upgrades only those domains that are created under install_dir/domains directory. Domains created in other locations are not upgraded.


Before starting the upgrade process, copy all the domain directories from their different locations to the install_dir/domains directory.

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:

    install_dir/bin/asupgrade --source install_dir/domains --target 
    install_dir --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:


Upgrade tool overwrites the content of a modified index.html of an instance (member of a cluster) (6386451)


The upgrade tool overwrites any existing index.html file for any server instance.


Back up your existing index.html files before running the upgrade tool, and then restore those files later.

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


When upgrading from Application Server 8.0PE to 9.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. This occurs because the domain.xml has changed between 8.0 and 9.1.


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

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 AS9.1 not from AS8.2 (6565825)


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


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

AS9.1 IFR upgrade tool doesn't migrate JES5U1 MQ store to the new var home (6573635)


The upgrade tool does not deal with upgrading databases or database tables in any form, nor will it ever support this. The resource references configurations are transferred and the Application Server should continue to work with the original database and tables. If you want to change the database or transfer database tables, use the tools that work with the databases in use.


Perform the following steps to migrate the MQ store:

Note –

Perform the following steps AFTER AS 8.2 has been shut down and AFTER the AS9.1 upgrade tool is run but BEFORE AS9.1 is started for the FIRST time. If you have already started AS 9.1 after the IFR install/upgrade, then DO NOT perform these steps as they will potentially destabilize the MQ message store.

  1. Copy the entire domains/domain1/imq subdirectory from the AS 8.x domains directory to the AS 9.1 domains directory.

  2. Ensure that the ownership of the directory and files is the same as the user that is going to be running the Application Server.

After pefrorming the above steps, Application Server 9.1 can be started and the MQ store in the Application Server 9.1. domains directory will be migrated from its JES5 U1 format to MQ 4.1 format. Note that the original JES5 U1 MQ store under AS 8.2 is preserved and unmodified by this procedure or by MQ4.1 upon startup by AS 9.1

Upgrade JES5 (AS 8.2) to AS 9.1. PS Community sample is broken, many javax.faces errors (6576700)


When upgrading from JES5 (Application Server 8.2) to Application Server 9.1, the Portal Server Community sample no longer works, and throws many javax.faces.application.ApplicationFactory errors.


Upgrading from Application Server 8.2 to 9.1 is not supported if Application Server 8.2 was installed with the JES5 Portal Server. Portal Server needs to be upgraded to Java ES 5 Update 1 prior the Application Server upgrade to 9.1.

AS91 IFR b58, Linux: /usr/jdk/entsys-j2se link is not updated after installing new Java via Installer (6591697)


When upgrading from Application Server 8.2 to 9.1 with the IFR installer on Linux platforms, selecting the Install JDK option, but after successful completion of the installation, most of the JES components stop working.


This issue only affects IFR installation of Application Server 9.1 in Linux platforms, and only when the Install JDK option is selected. To work around this issue, immediately after installation manually link /usr/jdk/entsys-j2se to the /usr/java/jdk1.5.0_12 directory.

AS9.1 IFR Win in-pace backup is not integrated with asupdate.bat form values checking - wrong path (6596412)


When performing an Application Server 9.1 IFR upgrade on Windows, in-place backup is not correctly integrated with asupdate.bat form values. Specifically, if you enter incorrect information in an ASupdate.bat GUI screen and then click Next, the upgrade installer tries to detect if it is an in-place upgrade. If yes, domain1 is moved to a backup directory prior upgrade. As the upgrade proceeds, and an error message is displayed as a result of the incorrect information. When you attempt to correct the error right away, the a path error is thrown because domain1 was already moved.


Either change the source directory to be the domain1_{timestamp} directory in {current source path}/backup or exit the installer with the Cancel button and start again.

AS9.1 IFR Windows, inline upgrade, Domain1 is deleted when asupgrade.bat used with short and long path (6596394)


(Windows only) If an earlier version of Application Server was installed using special characters or DOS-style short names in the program directory path, subsequent in-place upgrades to Application Server 9.1 will fail if those same directory path names are used.

For example, if Application Server 8.2 was installed in either:

C:\Program Files (x86)\dirs\appserver

Attempts to perform an in-place upgrade to 9.1 will fail because the installer cannot convert the short names or special characters to the required long name format.


Installing Application Server using a path name that contains special characters or the DOS-style short name truncation (such as progra~2) is strongly discouraged because it impedes subsequent upgrade installations. If such an installation exists, either reinstall it using long path names before upgrading, or install the new version of Application Server in an entirely new directory.

AS 9.1 IFR: Web UI Authentication Broken (6569813)


After an Application Server upgrade, the <jsp:forward> tag does not work as expected in Authenticate.jsp. The <jsp:forward> call produces an error in the server logs and a blank page is shown on the WebUI. The problem is that <jsp:forward> in Authenticate.jsp requires a page attribute like <jsp:forward page="${redirectPage}"/>, but the value being passed is a relative path like /registry/thin/{pagename}.jsp, which does not work even Authenticate.jsp is a pure JSP page.


After completing the Application Server upgrade, use the asadmin tool to run the following commands to set the <auth-realm> in domain.xml:

  1. Go to <appserver9.1-install-dir>/bin and run the following command:

    ./asadmin delete-auth-realm --host localhost --port 6489 certificate

    This removes the old auth-realm certificate, if one exists.

  2. Run the following command:

    ./asadmin create-auth-realm --terse=false --echo=true --interactive=true \
    --user admin --host localhost --port 6489 --classname \ \
    --property assign-groups=have.client.cert  certificate

    This creates the new <auth-realm> with the assign-groups property.

  3. Stop and restart the Application Server registry domain.

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.

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.

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


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

The auth-passthrough plugin function in Application 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 Application Server 9.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 Application Server 9.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 Application Server 9.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 Application Server 8.1 Update 2 instance with authPassthroughEnabled set to TRUE, SSL client authentication may be enabled on the web server proxy, and disabled on the proxied Application Server 8.1 Update 2 instance. In this case, the proxied Application Server 8.1 Update 2 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 Java System Web Server with Application Server 9.1 and Load Balancer on a Linux system. In such a case, after installing Application 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 Application 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" {