Troubleshooting a Sametime Advanced Server

In the event that a change is made to an IBM® WebSphere® Application Server component of the IBM Sametime® Advanced Server, WebSphere Application Server could fail to start.

Procedure

  1. Use a text editor to open the WebSphere Application Server file here: <was_home>\Appserver\profiles\STAdvanced_profile\config\cells\Cell_Name\nodes\<Node_Name\servers\STAdvanced_server_name\server.xml.
  2. In the server.xml file, search for jvmEntries. For example:
    <jvmEntries xmi:id="JavaVirtualMachine_1190064977109" 
verboseModeClass="false" verboseModeGarbageCollection="false" 
verboseModeJNI="false" initialHeapSize="1024" 
maximumHeapSize="1280" runHProf="false" debugMode="false" 
debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent 
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777" 
genericJvmArguments="-Xgcpolicy:gencon -Xgc:scvNoAdaptiveTenure,
scvTenureAge=8,stdGlobalCompactToSatisfyAllocate -Xmn256m" 
disableJIT="false"/>
    If the JVM arguments are incorrect, you must modify the genericJvmArguments attribute of the jvmEntries element of server.xml. You could leave it blank, to eliminate all errors, or try modifying the value of the attribute until it is correct. Two value here are the heap sizes. These values are set when you set the JVM garbage collection policy. But you can set them in the server.xml file as well. These values are the initialHeapSize with a recommended value of 1024, and maximumHeapSize, set to a recommended value of 1280.
  3. Save the file and restart the server.