Tomcat Core Issues on Solaris

I am running a Java Web Application in Tomcat 4.0.6 on Solaris 8 and the application is coring pretty regularly. Running a pstack on the core file gives the following output:

core 'core' of 12751:   /usr/j2se/bin/../bin/sparc/native_threads/java -Xmx1024m -Djava.endors
-----------------  lwp# 44 / thread# 33  --------------------
 ff3691f0 __sigprocmask (ff36b7f4, 0, 0, b2101d98, ff37c000, 0) + 8
 ff35dd0c _sigon   (b2101d98, ff3838a8, 6, b20fed84, b2101d98, ff38321c) + d0
 ff360d4c _thrp_kill (0, 21, 6, ff37c000, 21, ff2c0458) + f8
 ff24bce0 raise    (6, 0, 0, ffffffff, ff2c03c4, ff3831fc) + 40
 ff235984 abort    (ff2bc008, b20feed8, 0, fffffff8, 4, b20feef9) + 100
 fe6e4c4c __1cCosFabort6Fl_v_ (1, fe780000, 1, 31cf, 0, b3add4c4) + b8
 fe6e3e8c __1cCosbBhandle_unexpected_exception6FpnGThread_ipCpv_v_ (0, fe7bae60, fe791828, fe754b14, fe780000, 0) + 254
 fe6e78fc JVM_handle_solaris_signal (0, a42358, b20ffa00, fe780000, b, b20ffcb8) + 894
 ff36b118 __sighndlr (b, b20ffcb8, b20ffa00, fe6e5bc8, b2101e40, b2101e30) + c
 ff36811c sigacthandler (b, b2101d98, 0, 0, 0, ff37c000) + 708
 --- called from signal handler with signal 11 (SIGSEGV) ---
 b3add4c4 __1cLDOM_ElementMgetAttribute6kMrknJDOMString__1_ (b20ffe54, b20ffe5c, b20ffe58, 0, 0, b04398) + 14
 b2e82628 __1cFHWXMLRCXMLResultSetImplFParse6Mpkckb_v_ (3fb6418, b2100144, 0, b2e6c4a0, ff2fa08c, 49a92e0) + 1e0
 b2e5add4 __1cNCHWSessionTCPLGetSSOLists6Mpkcpcp3_l_ (0, 4a16110, 3fb6418, b21003d4, 0, 3fb6418) + 27c
 b2e27d28 __1cKCHWSessionLGetSSOLists6Mpkcpcp3_l_ (b21003e0, 4a16110, 4a4a1a8, b21003d4, ff2a74a8, 0) + 48
 b2e14bf4 __1cODF_GetSSOLists6FlpnMtagParamInfo_plp1_l_ (2, 4a72710, b210050c, b2100518, b2e14b58, 2) + 9c
 b2e047fc __1cIDispatch6FpclpnMtagParamInfo_plp2_l_ (4a02040, e, b2e14b58, b2e14b58, b2100518, 2) + 7c
 b2e0495c Java_com_*******_dispatch (a423dc, b21006a4, b21006a0, b210069c, ffffffff, b2100694) + cc
 fe7b4a34 __1cMStubRoutinesG_code1_ (b2101a00, b2101c38, a, f8c16230, d66e0, b2101b84) + 40c
 fe580ea0 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (b2101c30, fe780000, b2101b7c, a42358, d66e0, b2101c38) + 308
 fe58faf8 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (f8c16ea8, b2101b68, b2101b6c, fe780000, b2101c30, b2101b7c) + 150
 fe58f988 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (b2101c30, b2101c2c, b2101c28, b2101c1c, b2101c14, a42358) + 60
 fe58f910 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f8c16ea8, a42358, fe780000, b2101d38, 1e, e) + 120
 fe58f71c __1cKJavaThreadDrun6M_v_ (b2082000, fe789d5c, fe780000, 7fd98, a42358, 7fd98) + 3d8
 fe57f580 _start   (fe780000, b58a5d38, 0, 5, 1, fe401000) + 20
 ff36b01c _thread_start (a42358, 0, 0, 0, 0, 0) + 40

I only copied the section of the pstack from the appropriate lwp that is causing the core to happen. Obviously I am not expecting that anyone would be able to fix my application given only this information, but I am hoping that someone can tell me if there is anything in particular that this points to that I can look at more closely.

Thanks!
abhutianiAsked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
PAQed with no points refunded (of 500)

modulo
Community Support Moderator
0
 
yuzhCommented:
It looks like the JVM problem. You could try upgrading to the latest JDK and also apply the
J2SE patch.

also apply the Solaris latest Recommended Patch Cluster.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.