By definition, if the jvm crashes, it's a JVM bug (Unless you have loaded classes which use native code (like the Oracle OCI jdbc drivers).
I'd suggest you try the latest Sun JVM with and without hotspot, and if that fails have a go with the IBM JVM. Cheers Geoff > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of SeaWolf > Sent: Monday, 21 January, 2002 10:47 AM > To: Orion-Interest > Subject: stateful bean error > > > Hi... > > can anybody explain it to me, what is this all about.. > > at java.io.DataOutputStream.writeUTF > DataOutputStream.java(Compiled Code)) > at > java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:1529) > at > com.evermind.server.ejb.StatefulSessionObjectInfo.writeExterna > l(StatefulSession > ObjectInfo.java:31) > at > java.io.ObjectOutputStream.outputObject(ObjectOutputStream.jav > a(Compiled > Code)) > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java > (Compiled > Code)) > at > com.evermind.server.rmi.RMIOutputStream.writeType(RMIOutputStr > eam.java(Compiled > Code)) > at > com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java > (Compiled > Code)) > at > com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java(Compiled > Code)) > > My application server crash(segmentation violation) > when i invoke the stateful session bean. > > seawolf > > __________________________________________________ > Do You Yahoo!? > Send FREE video emails in Yahoo! Mail! > http://promo.yahoo.com/videomail/ >
