I ran across this myself recently and logged an SR with WM Support. I had already read through the core dumps to determine that IS seemed to be having an Just in Time Compiler (JITC) issue with a particular method. I followed the approach outlined in the attached PDF to identify the method that the JIT compiler was not able to process.
In my case the two core dump files showed the following:
- com.wm.util.coder.RPCBinCoder2._encode(RPCBinCoder2.java:467) – Invoked by “HTTP Handler ”
- com.wm.util.coder.RPCBinCoder2._encode(RPCBinCoder2.java:461) – Invoked by “Cron Daemon Pool2”
Based on the attached PDF, IBM recommends excluding the method from JITC using the following option:
JITC_COMPILEOPT=SKIP{com/wm/util/coder/RPCBinCoder2}{_encode}
Turns out that this is a known issue with IS 6.5 running as an NT Service
and is mentioned in the ReleaseNotes.html file that ships with IS 6.5.
See also this IBM Developerworks article for details on the JIT Compiler issue.
I added a new System-level environment variable named “” and set its value to the following:
SKIP{com/wm/util/coder/RPCBinCoder2}{_encode}{java/lang/Thread}{sleep}
Hopefully, this will do the trick.
Mark
Analyzing IBM JVM Core Dumps.pdf (396 KB)
#webMethods#webMethods-Archive#Integration-Server-and-ESB