Tomcat JVM Problem
Forum-
I have tomcat 5.0.28 installed on Solaris 9. I have a few Documentum applications running on this tomcat instance. Every 2-3 weeks, Tomcat dies, leaving the following scrubbed message:
core './core' of 27535: /opt/j2sdk1.4.2_05/bin/java -Dtrust.policy=/vol02/webtop53/trust.polic
-- lwp# 2 / thread# 2 --
ff31fc54 _lwp_kill (6, 0, fe27e928, 0, 23, ff00) + 8
ff2b6d50 abort(0, fe27e9b8, 0, fffffff8, 0, fe27e9e1) + 100
fef39fac __1cCosFabort6Fi_v_ (1, fefd204e, fe27ea68, feffa000, ff00f990, 35e4a0) + 80
fef380a4 __1cCosbBhandle_unexpected_exception6FpnGThread_ipCpv_v_ (0, b, feda8248, fe27f7c8, fef3d6bc, 0) + 2cc
fef3df18 JVM_handle_solaris_signal (feda8248, fe27f7c8, fe27f510, 3400, 356c, fef3ba24) + 8a4
ff385bac __sighndlr (b, fe27f7c8, fe27f510, b2efa8d8, 0, 0) + c
ff37f804 call_user_handler (b, fe27f7c8, fe27f510, 0, 0, 0) + 234
ff37f9b4 sigacthandler (b, fe27f7c8, fe27f510, fe27f974, e5aad688, 0) + 64
called from signal handler with signal 11 (SIGSEGV)
feda8248 __1cPContiguousSpaceWprepare_for_compaction6MpnMCompactPoint__v_ (b83ae720, b5800000, 0, 0, 0, 0) + 238
feda7fcc __1cKGenerationWprepare_for_compaction6MpnMCompactPoint__v_ (a96c0, fe27f974, f5aefd90, a94f4, ff02198c, 138a8) + 2c
feda7f64 __1cQGenCollectedHeapWprepare_for_compaction6M_v_ (a95a0, fefbfd19, 0, 1, 34680, 3800) + 3c
feda4d84 __1cMGenMarkSweepTinvoke_at_safepoint6FipnSReferenceProcessor_i_v_ (ff026ba4, 3941f2f8, 0, 4400, 4c00, 4ee4) + 28c
feda4ac8 __1cbCOneContigSpaceCardGenerationHcollect6MiiIii_v_ (aafd0, 0, 0, 84, 0, 0) + 34
fed8aeb4 __1cQGenCollectedHeapNdo_collection6MiiIiiiri_v_ (84, feffa000, 0, ff00b218, 0, 1) + 4f0
fed8a654 __1cbCTwoGenerationCollectorPolicyZsatisfy_failed_allocation6MIiiri_pnIHeapWord __ (a95a0, 3, ff00b218, 3c00, 3cb0, feffa000) + c8
fed8a54c __1cbAVM_GenCollectForAllocationEdoit6M_v_ (ab8fcf04, 28d800, 0, 22838e58, feffa000, 0) + 18
fed6c888 __1cMVM_OperationIevaluate6M_v_ (ab8fcf04, 28d978, feffa000, 37330, 3a6eac, fed696e0) + 8c
fed6c708 __1cIVMThreadSevaluate_operation6MpnMVM_Operation__v_ (d0330, ab8fcf04, 4a20, 4800, 4b3c, 0) + 84
fecc6fa8 __1cIVMThreadEloop6M_v_ (4000, 3c00, 3f3c, 3c00, 3ee4, 3800) + 3e0
fecc6970 __1cIVMThreadDrun6M_v_ (d0330, 0, ff019468, ffff8000, 0, 0) + 8c
fecc685c _start(d0330, 0, 0, 0, 0, 0) + 134
ff385854 _lwp_start (0, 0, 0, 0, 0, 0)
-- lwp# 3 / thread# 3 --
ff31fdf4 lwp_cond_wait (d1bd8, d1bc0, d1178, 0, 0, 0) + 8
fecd7900 __1cNObjectMonitorEwait6MxipnGThread__v_ (4800, 4b3c, 4800, 4a20, d1178, 4560) + 54c
fecd6e38 JVM_MonitorWait (d120c, fbd7fa7c, 0, 0, 0, 0) + 138
fa950f60 ? (bca0f658, fbd7fa8c, 0, c, bccd3618, bc7c8c80)
fa3975fc ? (5, 1, 4, fbd7fb20, be67a8e0, b73b3968)
f9c70b78 ? (fbd7fba8, 0, 0, f9c137e0, 33eed0, fbd7fb48)
f9c00118 ? (fbd7fc30, fbd7fe98, a, f584ea10, f9c0aae0, fbd7fdb8)
fecc7fc8 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_p nGThread__v_ (fbd7fe90, fbd7fcf8, fbd7fdb0, d1178, d1178, fbd7fd08)
+ 274
fecd6958 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJava CallArguments_pnGThread__v_ (feffa000, d1720, fbd7fda4, fbd7fda0, fb
d7fdb0, d1178) + 164
fecd67e4 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle _5pnGThread__v_ (fbd7fe90, fbd7fe8c, fbd7fe84, fbd7fe7c, fbd7fe74, d
1178) + 60
fecd676c __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (d1178, d1178, 927d8, d1720, 3239f4, fecd6570) + 128
fecd6598 __1cKJavaThreadDrun6M_v_ (d1178, ffffffe2, ff019468, ffff8000, 0, 0) + 288
fecc685c _start(d1178, 0, 0, 0, 0, 0) + 134
ff385854 _lwp_start (0, 0, 0, 0, 0, 0)
We've opened a support case with Documentum because of the interaction between tomcat and documentum, but support seems to think its a JVM problem. I don't have much expertise deciphering a file like this, I've been told its a garbage collection problem.
Does this look or sound familiar to anyone? Does anyone have any insight or configuration suggestions?
Thanks,
Erin
