09-19-05 12:50 PM
Thanks. That does look like the right direction.
Am I right, the problem appears to be with libjitc.so??? Or do I need to
look further in the dump?
Here is a snippet:
NULL -------------------------------------------------------------
-----------
0SECTION TITLE subcomponent dump routine
NULL ===============================
1TISIGINFO signal 11 received
1TIDATETIME Date: 2005/09/01 at 13:23:35
1TIFILENAME Javacore filename:
/opt/IBM/WebSphere/AppServer/profiles/default/javacore.20050901.132335.7604.
txt
NULL -------------------------------------------------------------
-----------
0SECTION XHPI subcomponent dump routine
NULL ==============================
1HPTIME Thu Sep 01 13:23:35 2005
1HPSIGRECV SIGSEGV received in ?? at 0x41fc3030 in
/opt/IBM/WebSphere/AppServer/java/jre/bin/libjitc.so. Processing terminated.
1HPFULLVERSION J2RE 1.4.2 IBM build cxia32142-20050609
NULL
1HPOPENV Operating Environment
NULL ---------------------
2HPHOSTNAME Host : serverx.
2HPOSLEVEL OS Level : 2.6.5-7.191-bigsmp.#1 SMP Tue Jun 28
14:58:56 UTC 2005
2HPLIBCVER glibc Version : 2.3.3
2HPCPUS Processors -
3HPARCH Architecture : (not implemented)
3HPNUMCPUS How Many : (not implemented)
3HPCPUSENABLED Enabled : 4
"Ken Hygh" <kenhygh@nc.rr.com> wrote in message
news:dga0se$542o$1@news.boulder.ibm.com...
> James Hevener wrote:
>
> Might be something in the WAS logs. If not, you might check to see if
> there's a javacore* file in one of the WAS directories. There's usually a
> javacore if WAS has a bad problem.
>
> Ken
[ Post a follow-up to this message ]
|