| Skip Navigation Links | |
| Exit Print View | |
|
Sun GlassFish Communications Server 2.0 Release Notes |
2. About Sun GlassFish Communications Server 2.0
3. Sun GlassFish Communications Server Known Issues and Limitations
Communications Server Administration
Domain creation stops on NFS server running 64-bit Linux (Issue Number 1961)
High CPU Utilization When There is Little or No Traffic (Issue Number 1966)
Communications Server instances start even if SIP/SIPS ports are not bound (Issue Number 998)
Communications Server does not use the JDK specified by --javahome option (Issue Number 789)
Using 3.5 GB Java heap causes instances to restart while traffic is on (Issue 1169)
Communications Server installer crashes on Linux (6739013)
SIP container unable to handle a CANCEL when it has sent a 100 response (Issue 712)
SIP sessions and HTTP sessions do not apply the same session expiration time model (Issue 1180)
SIP session lives on after container callback to sessionExpired (Issue 1265)
Communications Server first acts as a UAS, then as a proxy, and generates NOP (Issue 1432)
getLastAccessedTime method does not provide accurate results (Issue 1351)
SIP listener remains active for a certain duration after it is deleted (Issue 1294)
Communications Server throws exception when it receives a Contact header without "<>" (Issue 1489)
Communications Server throws exception at an invalid UUID value (Issue 1494)
Windows: Sometimes, UDP messages are not received by Communications Server (No id)
4. Sun GlassFish Enterprise Server Known Issues and Limitations
Communications Server file-based installer does not install Basic3pcc sample application. This application is available with the JAR installer.
No known solution.
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:
For Bourne shell:
MALLOC_CHECK_=0; export MALLOC_CHECK_
For bash shell:
export MALLOC_CHECK_=0
For csh, tcsh shell:
setenv MALLOC_CHECK_ 0
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 Communications Server on a 64–bit system, download the 32–bit JDK and use it to install Sun GlassFish Communications 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 Communications 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.
|