Issues with APM 9.6 and WAS 8.5.5/Redhat 7?

[Legacy User]

Hello All,

Has anyone had any issues getting the WAS 8.5.5 JVM/Introscope 9.6 agent started?  We're runnin these agents on zLinux (RedHat 7). I'm posing the question here because I cannot open a case at the moment.  I submit, and redirect to the case screen. I'll try that again later.

 

Thank you,
Geoffrey

[Haruhiko Davis]

Are you using Java 1.7?

[Legacy User]

No. We're using Java 1.6

[Haruhiko Davis]

Can you show us any of the error events from WAS or the agent?

[Legacy User]

Since there were no agent logs generated, the only error I see is in the native_stderr log.

Error opening zip file or JAR manifest missing : /opt/APM/Introscope9.6.0.0/wily/Agent.jar

JVMJ9TI064E Agent initialization function Agent_OnLoad failed for library instrument, return code -1

JVMJ9VM015W Initialization error for library j9jvmti26(-3): JVMJ9VM009E J9VMDllMain failed

[Thomas Wyszomierski]

Which version of agent.jar are you using? Sometimes using agentNoRedef.jar or
AgentNoRedefNoRetrans.jar helps if the jvm you are using lacks certain functionality the APM code expects.  See http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/TEC604200.aspx?intcmp=searchresult… for details

[Legacy User]

I've actually tried all variations of the Agent.jar. Unfortunately, they produce the same error.

[Billy Cole]

Is your agent directory under the opt/IBM/WebSphere or usr/IBM/WebSphere directory and is the entire contents of the agent directory owned and readable by the websphere user id?

 

Points of interest on the Java agent that caused us problems in the past is the configuration file on the JVM start path and the directory ownership.

 

Hope this helps,

Billy

[Anon Anon]

Hi Geoffrey,

 

Try restarting the Websphere JVM by enabling debug  mode & see if that helps.

[Legacy User]

Thank you all for you suggestions. Support and I worked through the issues and we're up and running.

[Anon Anon]

Can you update as to what was done to resolve the issue please?

[Legacy User]

The issue can be traced back to administrator error. At my last job, we scripted the installation and configuration of the agent. In my new job, I performed the install and configuration by hand before attempting to a scripted configuration.  I made two mistakes, both typos that caused the issue I encountered.