JVM Crash Explanation Needed

Hello everyone,

I have been having this jvm crash for a long time now and it has occurred randomly with little bit of differences in jvm thread trace. It has occurred again and this time I am using a SUSE Linux and Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02)

Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode).

The following is the thread trace that jvm generates after crashing:

Unexpected Signal : 11 occurred at PC=0xF7C18AD3

Function=JVM_handle_linux_signal+0x93

Library=/SIPostScanner/JDK/jre/lib/i386/client/libjvm.so

Current Java thread:

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlushBuffer(StreamEncoder.java:404)

at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:408)

at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)

- locked <0xec27d060> (a java.io.OutputStreamWriter)

at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)

at java.io.BufferedWriter.flush(BufferedWriter.java:230)

- locked <0xec27d060> (a java.io.OutputStreamWriter)

at java.io.PrintWriter.newLine(PrintWriter.java:256)

- locked <0xec2782a8> (a java.io.BufferedWriter)

at java.io.PrintWriter.println(PrintWriter.java:405)

at java.io.PrintWriter.println(PrintWriter.java:516)

- locked <0xec2782a8> (a java.io.BufferedWriter)

at abc.AbcWriter.run(AbcWriter.java:100)

At the end of the trace there is a line "abc.AbcWriter.run(AbcWriter.java:100)". That's my code and it is: printWriter.println("some command");And I am **** sure this line can not be the cause of the jvm crash, but then again I have no idea what is causing it.

If somebody could give me an explanation as to what it could be causing the crash, I would really appreciate it.

Thanks

Khurram

[2186 byte] By [khurramkhan1974a] at [2007-10-3 3:31:53]
# 1
Signal 11 is the dreaded SEGFAULT violation. The JVM has accessed memory that doesn't belong to it. This is almost certainly a bug.Brian
brian@cubik.caa at 2007-7-14 21:25:57 > top of Java-index,Core,Core APIs...
# 2

Yeah this is a bug .. please look at the following link .. I first started this topic at http://forum.java.sun.com/thread.jspa?threadID=763099 before realizing I was supposed to start this topic here on Networking forum.

Anyways, please go to the link mentioned to find out about the bug and the work around and its issues.

khurramkhan1974a at 2007-7-14 21:25:57 > top of Java-index,Core,Core APIs...