VCS WebSphere monitor cannot find the WebSphere processes because WebSphere instance is not configured properly

Article:TECH198415  |  Created: 2012-10-15  |  Updated: 2012-10-23  |  Article URL http://www.symantec.com/docs/TECH198415
Article Type
Technical Solution

Product(s)


Issue



VCS WebSphere monitor cannot find the WebSphere processes because WebSphere instance is not configured properly according to the VCS Websphere resource configuration


Error



When the VCS WebSphere resource is onlined through VCS, the WebSphere monitor entry point cannot find the WebSphere processes.   Even when the WebSphere instance is brought online manually outside VCS, the WebSphere monitor entry point still cannot find the WebSphere processes because of the incorrect WebSphere instance configuration.


Environment



VCS environment with WebSphere agent installed and WebSphere instance is running.


Cause



The WebSphere instance is not configured properly as specifed in the VCS WebSphere resource.   The WebSphere monitor entry point relies on the WebSphere resource attributes to form search string for the process name and arguments.   If the WebSphere instance is not configured according to the VCS WebSphere resource attributes, the monitor entry point will not be able to find the WebSphere processes.

For example, the following is the VCS WebSphere resource configuration.

WebSphere     cramsvt_gui-dmgr-wsr (
    Critical = 0
    ResLogLevel = TRACE
    ServerName = dmgr
    WAS_NODE = guiProfile_dmgr             <<<
    WAS_HOME = "/opt/app/WebSphere7/AppServer"          <<<
    User = n812xpius
    ServerProfile = "/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr"
    ServerType = DeploymentManager
    SecondLevelMonitor = 3
)


By setting he ResLogLevel to TRACE, we can find out why the monitor entry point cannot find the WebSphere process.   The following is the perl function that tries to find the WebSphere processes.   The search regular expression is formed by the WAS_HOME and WAS_NODE attributes.


sub IsWASProcessRunning
{
....
  #--------------------------------------
  # Form the filter to match WAS process
  #--------------------------------------
  my $sRegexWASName = GetServerNameRegex($sServerName);
  $sRegexWASName =~ s/\s+/\\s+/g;

  # Try FIRST filter

  my $sFilter =
        "^"
        .
        $sWASHome
        .
        "/.*/bin/.*java.*"
        .
        "com.ibm.ws.runtime.WsServer"
        .
        ".*"
        .
        "\\s+"
        .
        $sWASNode
        .
        "\\s+"
        .
        $sRegexWASName
        .
        "\\s*\$"
        ;
....
    #  IF NOT found, then try SECOND filter

    $sWASHome
    .
    "/.*/bin/.*java.*-Dwas.launcher.server=\\w:$sWASNode:$sRegexWASName"
    ;

 

According to the resource trace log, the monitor entry point found the following process.   Checking the process name and its arguments, it is found that the WebSpherr instance is configured with wrong WAS_NODE name.

 

ffdc:10044:Proc:GetLongProcessListHash:UID [39680] PID [27821] PPID [1] COMMAND [
/opt/app/WebSphere7/AppServer           <<< WAS_HOME
/java/bin/sparcv9/java -XX:+UnlockDiagnosticVMOptions -Dwas.status.socket=58684 -XX:+UnsyncloadClass -XX:MaxPermSize=256m -Declipse.security -Dosgi.install.area=/opt/app/WebSphere7/AppServer
-Dosgi.configuration.area=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/configuration
-Dosgi.framework.extensions=com.ibm.ws.eclipse.adaptors -Djava.awt.headless=true
-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider
-Xbootclasspath/p:/opt/app/WebSphere7/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/app/WebSphere7/AppServer/java/jre/lib/ext/ibmext.jar
-classpath /opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/properties:
/opt/app/WebSphere7/AppServer/properties:/opt/app/WebSphere7/AppServer/lib/startup.jar:
/opt/app/WebSphere7/AppServer/lib/bootstrap.jar:/opt/app/WebSphere7/AppServer/lib/jsf-nls.jar:/opt/app/WebSphere7/AppServer/lib/lmproxy.jar:
/opt/app/WebSphere7/AppServer/lib/urlprotocols.jar:/opt/app/WebSphere7/AppServer/deploytool/itp/batchboot.jar:
/opt/app/WebSphere7/AppServer/deploytool/itp/batch2.jar:/opt/app/WebSphere7/AppServer/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -Xms512m -Xmx512m
-Dws.ext.dirs=/opt/app/WebSphere7/AppServer/java/lib:/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/classes:
/opt/app/WebSphere7/AppServer/classes:/opt/app/WebSphere7/AppServer/lib:/opt/app/WebSphere7/AppServer/installedChannels:
/opt/app/WebSphere7/AppServer/lib/ext:/opt/app/WebSphere7/AppServer/web/help:
/opt/app/WebSphere7/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/opt/app/WebSphere7/AppServer/derby
-Dcom.ibm.itp.location=/opt/app/WebSphere7/AppServer/bin -Djava.util.logging.configureByServer=true
-Duser.install.root=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr
-Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/opt/app/WebSphere7/AppServer
-Dpython.cachedir=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/temp/cachedir
-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager
-Dserver.root=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr -Dcom.ibm.security.jgss.debug=off
-Dcom.ibm.security.krb5.Krb5Debug=off
-Djava.security.auth.login.config=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/properties/wsjaas.conf
-Djava.security.policy=/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/properties/server.policy com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher
com.ibm.ws.runtime.WsServer           <<< WsServer
/opt/app/WebSphere7/AppServer/profiles/guiProfile_dmgr/WAS/guiProfile_dmgr/config guiProfile_dmgr
hostABC_guiProfile_dmgr             <<< wrong WAS_NODE - should be guiProfile_dmgr
dmgr              <<< WASName / ServerName
]]
 


Solution



Customer needs to configure the WebSphere instance properly according to the VCS WebSphere resource configuration




Article URL http://www.symantec.com/docs/TECH198415


Terms of use for this information are found in Legal Notices