JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun GlassFish Communications Server 2.0 Release Notes

Document Information

1.  Overview

2.  About Sun GlassFish Communications Server 2.0

3.  Sun GlassFish Communications Server Known Issues and Limitations

4.  Sun GlassFish Enterprise Server Known Issues and Limitations

Administration

Communications Server does not detect conflicts with the heartbeat port of a cluster (Issue number 1967)

Description

Solution

Domain creation stops on NFS server running 64-bit Linux (Issue Number 1961)

Description

Solution

Performance degradation seen when a huge log file is rotated (6718611)

Description

Solution

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

Description

Solution

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

Description

Solution

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

Description

Solution

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

Description

Solution

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

Description

Solution

.asadmintruststore file not described in the documentation (6315957)

Description

Solution

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

Description

Solution

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

Description

Solution

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

Description

Application Client

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

Description

Solution

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

Description

Solution

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

Description

Solution

Bundled Sun JDBC Drivers

PreparedStatement errors (6170432)

Description 1

Solution 1

Description 2

Solution 2

Description 3

Solution 3

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

Description

Solution

Deployment

Autodeployment fails on a cluster sometimes (6610527)

Description

Solution

Application specific classloader not used by JSP compilation (6693246)

Description

Solution

Documentation

Javadoc Inconsistencies (various IDs)

Bundled ANT throws java.lang.NoClassDefFoundError (6265624)

Description

Solution

HTTP Service Statistics attributes discrepancies (7002258)

Description

Solution

SGCS 2.0: SIP container property "Reap interval" Missing documentation (6963298)

Description

Solution

SGCS 2.0: SIP Tutorial Doesn't Exclude 100 Trying Response (13721197)

Description

Solution

EJB

Resouce Injection does not work in HandlerChain (6750245)

Description

Solution

Java EE Tutorial

Java Persistence

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

Description

Solution

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

Description

Solution

Lifecycle Management

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

Description

Solution

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

Description

Solution

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

Description

Workaround

Logging

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

Description

Solution

Log level Setting for Persistence Cannot Be Made Persistent (13253247)

Description

Solution

Message Queue

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

Description

Solution

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

Description

Solution

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

Description

Solution

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

Description

Solution

Monitoring

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

Description

Solution

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

Description

Solution

Security

CA Certificate bundled with Communications Server 2.0 has expired (12287499)

Description

Solution

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

Description

Solution

General Vulnerability Assessment (Issue 17287)

Description

Solution

SSL termination is not working (6269102)

Description

Solution

Socket connection leak with SSL (6492477)

Description

Solution

Web Container

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

Description

Diagnostics

Solution

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

Description

Solution

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

Description

Solution

Web Services

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

Description

Solution

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)

Description

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.

Diagnostics

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.

Solution

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)

Description

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.

Solution

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)

Description

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:

at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.
exec(Execute.java:655) at org.apache.tools.ant.taskdefs.Execute.
launch(Execute.java:416) 
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:427) 
at org.apache.tools.ant.taskdefs.compilers.DefaultCompilerAdapter.
executeExternalCompile(DefaultCompilerAdapter.java:448) 
at org.apache.tools.ant.taskdefs.compilers.JavacExternal.execute
(JavacExternal.java:81) 
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842) 
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682) 
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:396)

Solution

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.