Troubleshooting
Problem
Symptom
Cause
Environment
Diagnosing The Problem
Resolving The Problem
reconfigure on the WAS server the APM 8.1 WAS agent and enable the Data Collector :
and reproduce the issue again.
Then, referring to APM knowledge Center link below
Apply the detailed steps below:
1. disable the JDBC instrumentation
go to the directory location:
/opt/ibm/apm/agent/yndchome/{dc_version}/runtime/<was_instance>/custom
for example:
/spatrol/apm/yndchome/7.3.0.14.02/runtime/was85.JazzSMNode01Cell.JazzSMNode01.JazzSMProfile.server1/custom
2. In the custom directory, update the toolkit_custom.properties file and
add the following property:
com.ibm.tivoli.itcam.toolkit.ai.enablejdbc=false
3. Restart the WAS server's JVM.
Notice :If the issue is not fixed, and your WAS application is still not working, collect the related data collector logs for further investigation.
for example, run:
/opt/ibm/apm/agent/lpl266/yn/bin/kyncollect.sh
It will produce an archive file, which contains the data collector main config files and logs.
You can then engage IBM support, or review the data collector logs to try and find out some clues on what is not right.
You can also refer to this other article for collecting more artifacts from WAS agent:
https://www.ibm.com/support/pages/node/1084317?lang=en&
Similarly as step 1 above, and as documented
you can try to disable other Byte Code Instrumentation's (BCI) type of Java EE API, like EJB, or JSP, or RMI, etc and see if that helpas further with your issue.
Document Location
Worldwide
Historical Number
TS003546302
Product Synonym
apm
Was this topic helpful?
Document Information
Modified date:
14 April 2020
UID
ibm16189753