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
Domain creation stops on NFS server running 64-bit Linux (Issue Number 1961)
Performance degradation seen when a huge log file is rotated (6718611)
Failed to Deploy Generic RA Resource Adapter against IBM MQ (Issue 6605)
Stand-alone instances sometimes obtain files from other instances (6698604)
Startup Message from the start-cluster command are too verbose (6728317)
The package-appclient script does not work if domain1 is not present (6171458)
Starting Application Server with additional JMX Agent is not supported (6200011)
.asadmintruststore file not described in the documentation (6315957)
Clustered instances fail to start due to a timeout in reaching the JMS broker (6523663)
Cannot display jmaki chart in Netscape 8.1.3, Mozilla 1.7 and Safari 2.0.4 browsers (6543014)
The create-domain command fails with custom master password in AIX (6628170)
Library JAR packaged in Application Client Archive overwrites MANIFEST file (6193556)
PreparedStatement errors (6170432)
Java DB is not started after machine reboot or Application Server start (6515124)
Autodeployment fails on a cluster sometimes (6610527)
Application specific classloader not used by JSP compilation (6693246)
Javadoc Inconsistencies (various IDs)
Bundled ANT throws java.lang.NoClassDefFoundError (6265624)
HTTP Service Statistics attributes discrepancies (7002258)
SGCS 2.0: SIP container property "Reap interval" Missing documentation (6963298)
SGCS 2.0: SIP Tutorial Doesn't Exclude 100 Trying Response (13721197)
Resouce Injection does not work in HandlerChain (6750245)
TopLink expects my Collection field/property to be cloneable (Issue Tracker 556)
GenerationType.IDENTITY and DataDirect Driver with SyBase (Issue Tracker 2431)
Setting ejb-timer-service property causes set command to fail (6193449)
Error thrown when list JMS physical destinations within non-DAS config (6532532)
Win2003 only: Non-paged pool leak memory, breaking tcp stack and richaccess test (6575349)
Setting debug statement for access,failure causes hang in Application Server startup (6180095)
Log level Setting for Persistence Cannot Be Made Persistent (13253247)
Server Does Not Start If MQ Broker is Not Started (6740797)
MQ broker fails to start with cluster profile on Linux (6524871)
Mismatch of old and new classes is created when imqjmsra.jar is loaded before upgrade (6740794)
Open JNDI Browsing from Admin UI dumps a huge amount of exceptions in the server.log (6591734)
CA Certificate bundled with Communications Server 2.0 has expired (12287499)
OutofMemory Error in SSL Scenarios During Heavy Stress (JDK 6 Issue 23)
General Vulnerability Assessment (Issue 17287)
SSL termination is not working (6269102)
Socket connection leak with SSL (6492477)
Unable to compile JSP page on resource constrained servers (6184122)
wscompile fails with "package javax.xml.rpc does not exist" on JDK6 u4 b3 (6638567)
This section describes known application client issues and associated solutions.
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.
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
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 Communications Server, such that the selector is unwrapped before the keyFor API is called. This enables the keyFor to succeed until JDK bug is fixed.