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

Lifecycle Management

This section describes known lifecycle management issues and associated solutions.

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

Description

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.

Solution

Use the default values for these properties, as follows:

minimum-delivery-interval(default)=7000
redelivery-interval-in-millis(default)=5000

Values other than these defaults will generate an error.

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

Description

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

Solution

This is expected behavior. In Communications Server 2.0, 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)

Description

(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.

Workaround

There are two workarounds to this issue: