n/a

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.

n/a

WebLogic SIP Server MIB objects are read-only. You cannot modify a WebLogic SIP Server configuration using SNMP.

n/a

This version of Weblogic SIP Server exhibits two behaviors that do not conform to the JSR 116 specification:

n/a

If you attempt to install WebLogic SIP Server 3.0 on Fedora Core 3 or 4 with selinux running, the installer throws a java.lang.UnsatisfiedLinkError exception. You cannot install WebLogic SIP Server while selinux is active.

n/a

If you configure two or more data tier replicas using the default WebLogic Server Listen Address configuration (which specifies no listen address), multiple 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 data tier server instance.

n/a

In a WebLogic SIP Server installation with two engine tier nodes and two data tier nodes in a partition (two replicas), if the connection to the data tier becomes "split" such that each engine tier server can only reach a different data tier node, one of the replicas is forced offline. To recover from this situation, always configure the Node Manager utility to restart 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.

CR267829

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 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).

CR290540, CR303769

WebLogic SIP Server ignores any encoding set through the SipServletMessage.setCharacterEncoding() method. The server only honors the encoding set using the contentType argument of the setContent() method.

Also, in version 3.0, setCharacterEncoding() no longer throws an UnsupportedEncodingException. Existing Servlet code that calls this method and has a catch claus for UnsupportedEncodingException must be modified before recompiling for deployment to WebLogic SIP Server 3.0.

CR291406

If you are running WebLogic SIP Server on a Windows platform with the JRockit JVM, you must disable JRockit native IO in order to use SSL. To do so, either specify the -Xnativethreads command line option when starting the server, or add the following stanza to the config.xml file for your domain:

<server>

<name>myserver</name>

<native-io-enabled>false</native-io-enabled>

<listen-address></listen-address>

<network-access-point/>

...

</server>

If you do not disable native IO, you will receive an exception similar to:

java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.

CR294126

When an application in a replicated domain configuration is undeployed, WebLogic SIP 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.

CR297764

This release deprecates the use of earlier domain configuration scripts that were located in WLSS_HOME/common/templates/silent_scripts. Domain configuration templates are now configured using WLST-based scripts located in WLSS_HOME/common/templates/scripts/wlst.

CR305182

When using WebLogic SIP Server with geographically-redundant installations, each write to a secondary site logs an error message similar to:

<Dec 13, 2006 12:48:08 PM PST> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>

To avoid these error messages, follow the instructions in Enable trust between domains in the WebLogic Server 9.2 documentation to establish a trusted relationship between the primary and secondary site domains.

CR300715

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.

CR302859

If you use SCTP with IPv4 on Solaris, use the -Dsctp.preferIPv4Stack=true Java option when starting the server. You can either edit your startup script to include the option, or set the environment variable:

export JAVA_OPTIONS=-Dsctp.preferIPv4Stack=true

If you do not use this Java option, you may be unable to connect

CR303194

On Windows platforms, if you install the WebLogic SIP Server product nested inside of other folders, you may be unable to load the Administration Console extension due to the length of the path being too long. To work around this problem, set the following environment variable before starting the Administration Server:

set JAVA_OPTIONS=-Dweblogic.j2ee.application.tmpDir=d:/TEMP

CR304056

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