Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Oracle Communications Converged Application Server Known Issues

The following table summarizes known issues and problems in Oracle Communications Converged Application Server.

Note: This section describes only those issues associated with the SIP Servlet container and data replication features of Oracle Communications Converged Application Server. See also the WebLogic Server Known and Resolved Issues for information about known problems with Oracle WebLogic Server 10g Release 3, which provides the underlying OA&M and Java EE5 capabilities of Oracle Communications Converged Application Server.
Table 3-1 Known Issues
Change Request Number
In this release, you must use to set the SIP Server environment correctly. For example:
This correctly sets the environment by sourcing both WLSSCommEnv.cmd and
Additionally for NodeManager to work properly, you must manually edit the script to source wlsscommEnv.cmd/sh.
By default, new Diameter network channels are created with a default Idle Connection Timeout value of 65 seconds. Change this attribute from the default in order to ensure that connections are not dropped and recreated every 65 seconds. See Creating Network Channels for the Diameter Protocol.
Oracle Communications Converged Application Server MIB objects are read-only. You cannot modify a Oracle Communications Converged Application Server configuration using SNMP.
This version of Oracle Communications Converged Application Server exhibits two behaviors that do not conform to the JSR 116 specification:
  • MIME content is returned as a String object, rather than as a javax.mail.Multipart object as encouraged by the specification.
  • isPersistent, used for re-instantiating ServletTimer after server restarts, is not implemented.

Also, Oracle Communications Converged Application Server does not support dialog stateless proxies, an optional feature described in the API JavaDoc for the Proxy interface, setStateful() method:

“This proxy parameter is a hint only. Implementations may choose to maintain transaction state regardless of the value of this flag, but if so the application will not be invoked again for this transaction.”

If you attempt to install Oracle Communications Converged Application Server 3.0 on Fedora Core 3 or 4 with selinux running, the installer throws a java.lang.UnsatisfiedLinkError exception. You cannot install Oracle Communications Converged Application Server while selinux is active.
If you configure two or more SIP data tier replicas using the default WebLogic Server Listen Address configuration (which specifies no listen address), multiple SIP data tier instances on the same machine cannot connect to one another. This problem occurs because, using the default Listen Address configuration, JNDI objects in the first booted server bind to all local IP addresses.
To avoid this problem, always enter a valid IP address for each configured SIP data tier server instance.
In a Oracle Communications Converged Application Server installation with two engine tier nodes and two SIP data tier nodes in a partition (two replicas), if the connection to the SIP data tier becomes “split” such that each engine tier server can only reach a different SIP data tier node, one of the replicas is forced offline. To recover from this situation, always configure the Node Manager utility to restart SIP data tier replicas automatically when a replica fails. This enables the replica to rejoin its associated partition and update its copy of the call state data without having to manually restart the server.
The SIP Servlet v1.0 Specification states: “Containers may send the request asynchronously in which case sending may fail after the send method has returned successfully. In this type of situation, the container will generate its own final response. In this particular case, a 404 response would be appropriate.” Oracle Communications Converged Application Server sends requests asynchronously but does not deliver a 404 Not Found response to an application if a transport failure occurs. To work around this problem, applications should rely on the 408 Request Timeout response instead of 404.
During an overload condition, Oracle Communications Converged Application Server may log messages similar to:
<ACK received in state PROCEEDING:class=[ServerTransaction], 
objid=[25292416], key=[z9hG4bKc227250e04757a91cbdde388192e21f5], 
state=[3,PROCEEDING], method=[INVITE]>
This occurs even if the ACK could be safely ignored (for example, if the ACK was generated by the server for a 503 response). There is no workaround to this problem, but it should occur only rarely (during overload conditions).
When starting a replicated domain, if a partition has no running replicas and two replicas are started at the same time, the second replica shuts down if one or more engine tier servers are already running. To avoid this problem, always start all SIP data tier servers before starting any engine tier servers in a replicated domain.
CR272491, CR189353
On Linux and UNIX systems, the default TCP connection timeout interval is usually very long and can cause Managed Servers to disconnect from the Administration Server under certain failure conditions.
Specifically, if a single Managed Server in a domain fails abruptly or is disconnected from the network (for example, due to a removed network cable), the Administration Server tries to communicate to the failed server for the length of the TCP connection timeout value. During this time, the Administration Server does not send heartbeat messages to the remaining Managed Servers in the domain. Failing to send the heartbeat messages causes the remaining Managed Servers to consider the Administration Server as being offline, and they disconnect from the Administration Server. This finally causes the Administration Server to throw PeerGoneExceptions for the disconnected servers after the TCP timeout interval has been reached and the connection is closed.
To work around this issue without changing the operating system TCP connection timeout value, use the -Dweblogic.client.SocketConnectTimeoutInSecs startup option when booting the Administration Server. BEA recommends using a value of 60 seconds to avoid numerous missed heartbeats (-Dweblogic.client.SocketConnectTimeoutInSecs=60).
When an application in a replicated domain configuration is undeployed, Oracle Communications Converged Application Server uses timer processing to clean up the remaining call state data for the application. However, in a non-replicated configuration, the server attempts to invalidate remaining session data but does not destroy call states associated with the application; this may result in the server “leaking” call states that existed during application undeployment.
Testing on Solaris platforms has shown that the following JVM arguments to improve performance with the Sun JVM for replica servers:
-server -Xms1024m -Xmx1024m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
For engine tier servers, these example arguments have shown to improve performance:
-server -Xms768m -Xmx768m -XX:+UseParallelGC -XX:MaxGCPauseMillis=400 -XX:+DisableExplicitGC
Note that these JVM settings have only been tested on Solaris platforms. For other platforms, begin with the example JVM arguments described in Tuning JVM Garbage Collection for Production Deployments.
In order to use SCTP with IPv4 on Solaris, you must set the -Dsctp.preferIPv4Stack=true Java option when starting the server. You can edit your startup script to include this option, or set the environment variable:
export JAVA_OPTIONS=-Dsctp.preferIPv4Stack=true
If you install the 64-bit version of Oracle Communications Converged Application Server installer package on Solaris, you must add the -d64 option with the Sun JDK in order to specify 64-bit mode. If you omit the -d64 option, the Sun JDK automatically defaults to 32-bit mode and the installer fails to install required 64-bit native libraries. This yields the following error on startup:
<Oct 4, 2007 4:54:28 AM EDT> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that a native performance library is in: path>

  Back to Top       Previous  Next