Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

WebSphere stack overflow prevents agent communication after successful auto-discovery completes

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5.1.2
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    AIX 5.3 1 6 00F6191D4C00
    IBM WebSphere Application Server - ND Version 6.1.0.35

    WebSphere Version 7.0.0.17
    /opt/WebSphere/AppServer/java/bin/java -version "1.6.0_24"
    solaris sparcv9 (SR9 FP1)
  • Case Links:
  • Regression:
    No

Description

Agent starts and runs, auto-discovery is complete and successful. and WebSphere is accepted into inventory.

A stack overflow results when clicking OK after providing username and password to configure Dmgr as a result of missing ibm classes.

A workaround was discovered by an onsite employee, we need to incorporate the fixes into our plugin.

Activity

Hide
Jason Konicki added a comment -

This is directly from the support ticket:

Issue: SUPPORT-10941 StackOverflowError starting agent on AIX
https://jira.hyperic.com/browse/SUPPORT-10941

Synopsis: Agent starts and runs, auto-discovery is complete and successful. and WebSphere is accepted into inventory.

A stack overflow results when clicking OK after providing username and password to configure Dmgr as a result of missing ibm classes.

Environment:

OS: AIX 5.3 1 6 00F6191D4C00

WebSphere version: IBM WebSphere Application Server - ND Version 6.1.0.35
WebSphere user: root

Name IBM WebSphere Application Server - ND
Version 6.1.0.35
ID ND
Build Level cf351044.07
Build Date 11/5/10

JVM: build pap64devifx-20101008a (SR12 FP2)

java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pap64devifx-20101008a (SR12 FP2 ))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423ifx-20101008 (JIT enabled)
J9VM - 20101007_66049_BHdSMr
JIT - 20100623_16197ifx1_r8
GC - 20100211_AA)
JCL - 20101008

HQ version: 4.5.1.2-EE

Agent version: 4.5.1.2-EE
Agent user: root

Notes:

Global Security enabled for Dmgr
Global Security not enabled for nodeagent

Actions Taken:

Applied updated WebSphere plugin from SUPPORT-10619, and the updated plugin did not resolve the issue.

Used plugins.include=websphere directive to load only the WebSphere plugin.

The following workaround was applied using the updated WebSphere plugin:

1.) Classes were not found, added "/usr/WebSphere64/AppServer/plugins/*.jar" to pick up ws.runtime-6.1.0-jar (brute-force it picked up all)

Added to hq-agent-no-wrapper.sh

for i in `ls /usr/WebSphere64/AppServer/plugins/*.jar`
do
CLIENT_CLASSPATH="${CLIENT_CLASSPATH}:${i}"
done
CLIENT_CLASSPATH="${CLIENT_CLASSPATH}:${AGENT_LIB}:${WAS_CLASSPATH}"

2.) Agent started without the wrapper, using the the following startup script to set environment.

Sourced /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh to pick up WebSphere environment variables.

Added to $WAS_EXT_DIRS and $WAS_HOME/lib/WMQ/java/lib to HQ_JAVA_OPTS

These were both required to address the class not found issue.

#!/usr/bin/ksh
#Modify this path to the actual location of setupCmdLine.sh
#This command should generate the variables WAS_HOME and WAS_EST_DIRS source /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh
. /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh
export HQ_JAVA_HOME=/usr/WebSphere64/AppServer/java
export HQ_JAVA_OPTS="-Djava.ext.dirs=$HQ_JAVA_HOME/jre/lib/ext:$WAS_EXT_DIRS:$WAS_HOME/lib/WMQ/java/lib"

/usr/WebSphere64/hyperic/hyperic-hqee-agent-4.5.1.2/bundles/agent-4.5.1.2/bin/hq-agent-nowrapper.sh start >startup.log 2>&1 &

Note that classloading logging provided the information about the missing classes.

Customer is now successfully monitoring WebSphere using the workaround.

Show
Jason Konicki added a comment - This is directly from the support ticket:
Issue: SUPPORT-10941 StackOverflowError starting agent on AIX https://jira.hyperic.com/browse/SUPPORT-10941 Synopsis: Agent starts and runs, auto-discovery is complete and successful. and WebSphere is accepted into inventory. A stack overflow results when clicking OK after providing username and password to configure Dmgr as a result of missing ibm classes. Environment: OS: AIX 5.3 1 6 00F6191D4C00 WebSphere version: IBM WebSphere Application Server - ND Version 6.1.0.35 WebSphere user: root Name IBM WebSphere Application Server - ND Version 6.1.0.35 ID ND Build Level cf351044.07 Build Date 11/5/10 JVM: build pap64devifx-20101008a (SR12 FP2) java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pap64devifx-20101008a (SR12 FP2 )) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc64-64 j9vmap6423ifx-20101008 (JIT enabled) J9VM - 20101007_66049_BHdSMr JIT - 20100623_16197ifx1_r8 GC - 20100211_AA) JCL - 20101008 HQ version: 4.5.1.2-EE Agent version: 4.5.1.2-EE Agent user: root Notes: Global Security enabled for Dmgr Global Security not enabled for nodeagent Actions Taken: Applied updated WebSphere plugin from SUPPORT-10619, and the updated plugin did not resolve the issue. Used plugins.include=websphere directive to load only the WebSphere plugin. The following workaround was applied using the updated WebSphere plugin: 1.) Classes were not found, added "/usr/WebSphere64/AppServer/plugins/*.jar" to pick up ws.runtime-6.1.0-jar (brute-force it picked up all) Added to hq-agent-no-wrapper.sh
for i in `ls /usr/WebSphere64/AppServer/plugins/*.jar`
do
CLIENT_CLASSPATH="${CLIENT_CLASSPATH}:${i}"
done
CLIENT_CLASSPATH="${CLIENT_CLASSPATH}:${AGENT_LIB}:${WAS_CLASSPATH}"
2.) Agent started without the wrapper, using the the following startup script to set environment. Sourced /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh to pick up WebSphere environment variables. Added to $WAS_EXT_DIRS and $WAS_HOME/lib/WMQ/java/lib to HQ_JAVA_OPTS These were both required to address the class not found issue.
#!/usr/bin/ksh
#Modify this path to the actual location of setupCmdLine.sh
#This command should generate the variables WAS_HOME and WAS_EST_DIRS source /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh
. /usr/WebSphere64/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh
export HQ_JAVA_HOME=/usr/WebSphere64/AppServer/java
export HQ_JAVA_OPTS="-Djava.ext.dirs=$HQ_JAVA_HOME/jre/lib/ext:$WAS_EXT_DIRS:$WAS_HOME/lib/WMQ/java/lib"

/usr/WebSphere64/hyperic/hyperic-hqee-agent-4.5.1.2/bundles/agent-4.5.1.2/bin/hq-agent-nowrapper.sh start >startup.log 2>&1 &
Note that classloading logging provided the information about the missing classes. Customer is now successfully monitoring WebSphere using the workaround.
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 4 days ago