Communications Server instances starts up even if it cannot bind to a SIP or SIPS port.
Ensure that ports are free before starting server instance(s). Check the log files (server.log) to ensure that there have not been any SIP container errors or exceptions during the startup.
For details on how to view log files, see TBDlink.
You can use a preinstalled JDK instead of the default version for the installation by using the ––javahome option. Communications Server, by default, uses the JDK version from as-install/jdk.
The AS_JAVA variable in the asenv.conf file always points to as-install/jdk. If you want to use a different JDK version, update the asenv.conf file manually and changed the value of AS_JAVA.
When JVM heap size is set to 3.5 GB, Communications Server instances fail and restart when they receive traffic.
Ensure that the maximum JVM heap size is set to 3.0 GB or less. For details on how to change the JVM heap size, see TBDlink
On Solaris platforms, Communications Server calculates CPU usage based on the number of available processors and the per-core CPU usage. However, Communications Server takes into account the static value of number of cores and not the number of cores that are used by the JVM.
Recalculate the CPU threshold values if you are not using all the cores in the machine.
If you log in as root with the Bourne shell (/bin/sh) and run asadmin commands, then log out of the console window, all the domain administration server (DAS), node agent, and instance processes are killed. This is because in the Bourne shell all child terminals inherit the TTY by default, so when the terminal is logged out, all child processes are killed too.
Before running any asadmin commands, do the following:
Log in to the server.
Change to K shell:
# exec /bin/ksh
In K shell, run all the asadmin commands to bring up the DAS, node agents, and instances.