The JVM is core dumping with the following as the current thread:
1XMCURTHDINFO Current Thread Details
NULL ----------------------
3XMTHREADINFO "Cron Daemon Pool1" (TID:0x101EB468, sys_thread_t:0x65AD3E0, state:R, native ID:0x13E0) prio=5
4XESTACKTRACE at com.wm.util.coder.RPCBinCoder2._encode(RPCBinCoder2.java:643)
4XESTACKTRACE at com.wm.util.coder.RPCBinCoder2._encode(RPCBinCoder2.java:467)
4XESTACKTRACE at com.wm.util.coder.RPCBinCoder2.encode(RPCBinCoder2.java:300)
4XESTACKTRACE at com.wm.util.queue.FSValuesHash.writeEntry(FSValuesHash.java:335)
4XESTACKTRACE at com.wm.util.queue.FSValuesHash.add(FSValuesHash.java:153)
4XESTACKTRACE at com.wm.util.queue.FSMTValuesHash.add(FSMTValuesHash.java:271)
4XESTACKTRACE at com.wm.util.queue.FSMTValuesHash.put(FSMTValuesHash.java:369)
4XESTACKTRACE at com.wm.app.repo.LocalRepositoryContext.put(LocalRepositoryContext.java:205)
4XESTACKTRACE at com.wm.app.repo.RepositoryContext.put(RepositoryContext.java:136)
4XESTACKTRACE at com.wm.app.b2b.util.RepoHelper.putInRepo(RepoHelper.java:201)
4XESTACKTRACE at com.wm.app.b2b.server.cluster.SessionStore.addSession(SessionStore.java:169)
4XESTACKTRACE at com.wm.app.b2b.server.cluster.ClusterManager.addSession(ClusterManager.java:619)
4XESTACKTRACE at com.wm.app.b2b.server.StateManager.run(StateManager.java:235)
4XESTACKTRACE at com.wm.util.pool.PooledThread.run(PooledThread.java:105)
4XESTACKTRACE at java.lang.Thread.run(Thread.java:568)
Has anyone seen this? Or even better found the cause or solution?
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:
As a follow-up to this question, I would like to clarify how I can generate a JVM core dump or hs_err_pid file.
I am running IS using a Sun JVM but it does not generate such files.
The IS runs as a Service on a Windows 2000 server and the only option seems to be as follows:-
stop IS
remove -Xrs switch from server.bat file
start IS in foreground on Windows server
wait for crash
However, I would like to be able to perform this with less manual input and maybe set a switch on the IS start command to produce a JVM dump file without staying logged on to the server!!!
You can generate a thread dump (not technically a core dump since contents of memory are not written to a file) by sending a “kill -3 process_id” to a unix process or by pressing CTRL-\ in Unix or CTRL-BREAK from the Windows command prompt.
Hello,
I am just getting the time to look at this and have applied the env variable fix to see if that helps while considering upgrading to a new jvm. We are running included ibm 1.4.2 (48.0) with is 6.5 sp3 build 394.
Will this be an option to take out when switching over to later version or different vendor jvm? Thank you. Good day.