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

Communications Server 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

sip.ssl.port property in asadmin create-domain --help is incorrectly documented as sips.port (Issue Number 12297064)

Description

Solution

High CPU Utilization When There is Little or No Traffic (Issue Number 1966)

Description

Solution

Communications Server instances start even if SIP/SIPS ports are not bound (Issue Number 998)

Description

Solution

Communications Server does not use the JDK specified by --javahome option (Issue Number 789)

Description

Solution

Using 3.5 GB Java heap causes instances to restart while traffic is on (Issue 1169)

Description

Solution

Communications Server wrongly reports CPU usage when using only one of the cores of a multi-core system (Issue 1344)

Description

Solution

Converged Load Balancer

SEVERE messages in logs due to dynamic reconfiguration of converged load balancer after application deployment (Issue 1161)

Description

Solution

When complete URI is used, the BEKey parameter in the Contact header is not correctly escaped (Issue 1466)

Description

Solution

Installation

Communications Server file-based installer does not install Basic3pcc sample application (Bug number 6894932)

Description

Solution

Communications Server installer crashes on Linux (6739013)

Description

Solution

Installation with 64-bit JDK Fails (6796171)

Description

Solution

Security

Communications Server throws exception when trust-auth-realm-ref property is not specified in sun-sip.xml (CR 6786131)

Description

Solution

SIP Container

SIP container unable to handle a CANCEL when it has sent a 100 response (Issue 712)

Description

Solution

SIP sessions and HTTP sessions do not apply the same session expiration time model (Issue 1180)

Description

Solution

SIP session lives on after container callback to sessionExpired (Issue 1265)

Description

Solution

Communications Server first acts as a UAS, then as a proxy, and generates NOP (Issue 1432)

Description

Solution

getLastAccessedTime method does not provide accurate results (Issue 1351)

Description

Solution

SIP listener remains active for a certain duration after it is deleted (Issue 1294)

Description

Solution

Communications Server throws exception when it receives a Contact header without "<>" (Issue 1489)

Communications Server throws exception at an invalid UUID value (Issue 1494)

Description

Solution

Windows: Sometimes, UDP messages are not received by Communications Server (No id)

Description

Solution

SIP Session Replication

Possible deadlock if a converged application uses SAS object as synchronization lock (Issue number 1954)

Description

Solution

4.  Sun GlassFish Enterprise Server Known Issues and Limitations

Chapter 3

Sun GlassFish Communications Server Known Issues and Limitations

This chapter describes known problems and associated solutions for the Communications Server software. If a summary statement does not specify a particular platform, the problem applies to all platforms. This information is organized into the following sections: