SIGSEGV 11* segmentation violation

Question

I'm on a Sco Unixware 7.1.3 platform using
WLS 7SP1 with SCO JDK1.3.1_06.
This configuration is running at most of our stores, and has
been running at this one store for 2 months with no problem until 4 days ago.
When starting WLS, it keeps aborting and core dumping and restarting the WLS
server after each core dump. Just finally got in my stdout log file (see below
peice of log), but now crashes the unixware box.
Has anyone else seen this problem or know what causes it?
Thanks in advance.
Starting WebLogic Server...
<Jul 16, 2003 4:58:17 PM EDT> <Notice> <Management> <140005> <Loading configuration
/appserver/user_domains/wls700/storedomain/./config.xml>
<Jul 16, 2003 4:59:37 PM EDT> <Notice> <Security> <090082> <Security initializing
using realm myrealm.>
<Jul 16, 2003 4:59:51 PM EDT> <Notice> <WebLogicServer> <000327> <Starting WebLogic
Admin Server "MainServer" for domain "storedomain">
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0xA3DF2478]
     stackpointer=80454b4
Full thread dump Classic VM (SCO-UNIX-J2SE-1.3.1_06:*FCS*:20021212, native threads):
"CoreHealthMonitor" (TID:0xb4fa0638, sys_thread_t:0x9783670, state:CW, native
ID:0x3d) prio=5
     at java.lang.Thread.sleep(Native Method)
     at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java,
Compiled Code)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" (TID:0xb4f06258, sys_thread_t:0x951faf8,
state:CW, native ID:0x3c) prio=5
     at java.lang.Object.wait(Native Method)
     at java.lang.Object.wait(Object.java, Compiled Code)

Answer 1

hi,
i have a similar problem on my linux-server: i am runninig a java-program that parses a large xml-file (>20MB) and updates a database in background with the data of this xml-file. the programm starts without any problems, but after processing about the half file and allocating a lot of memory (about 400 to 500 MB) there occures the following error:
SIGSEGV 11 (*) segmentation violation
si_signo [11]: SIGSEGV: (*) segmentation violation
si_errno [0]: Success
si_code [1]: SEGV_MAPERR [addr: 0x1]
stackpointer=0xbffc7af8
Full thread dump Classic VM (J2RE 1.2.2 IBM build cx122-20010504, native threads):
"Finalizer" (TID:0x402ca728, sys_thread_t:0x80f4540, state:S, native ID:0xc04) prio=8
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Finalizer.java(Compiled Code))
at java.lang.ref.Finalizer.access$1(Finalizer.java(Compiled Code))
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java(Compiled Code))
"Reference Handler" (TID:0x402ca768, sys_thread_t:0x80ea7f8, state:S, native ID:0x803) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:426)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java(Compiled Code))
"Signal dispatcher" (TID:0x402ca7a8, sys_thread_t:0x80ea638, state:S, native ID:0x402) prio=5
the strange thing is that the program seemed to work correctly with smaller xml-files in former times. now the xml-files have permanetly grown and it seems to me that the programm has not enough handles or something to process the whole file.
could it be a database-problem? i am using a db2 and before this problem appeared, i reduced the amount of the following database-parameters: DBHEAP, APP_CTL_HEAP_SZ, STMTHEAP, APPLHEAPSZ, MAXFILOP in order to reduce the "memory-waste". i also have tried to call the garbage collector more often so that memory is freed.
can anybody help me please??
rde