| 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)
Installation with 64-bit JDK Fails (6796171)
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
If you modify the configuration of the converged load balancer on a target and you redeploy the applications on that target, the instance logs will show SEVERE messages.
These messages do not affect the functioning of the converged load balancer or the instances. Ignore these messages.
When you use a converged load balancer with a data-centric rules file that returns a complete URI for the BEKey parameter, he BEKey parameter in the Contact header is not correctly escaped. The “:” character is not correctly escaped as specified in RFC 3261.
No known solution.
|