hmm, very interesting. What other processes are running outside the VM? do you have process monitors, intrusion detection or other memory/IO intensive processes running on the same box? you can rule out native drivers as a possible cause. the VM still could be causing it. tomcat is most likely not the cause. that still leaves a lot of variables you have to track down. what are the exact system specs again? peter
jean-frederic clere <[EMAIL PROTECTED]> wrote: Peter Lin wrote: > > as someone else mentioned, these types of seg fault errors have been the > result of database drivers in the past. Specifically, using native > drivers. I am not using any native drivers. > > I am aware of this type of behavior occuring with other drivers like JMS > that wrap native code. Make sure your database driver isn't the cause. > Try using a third party pure java jdbc driver and see if the same > behavior occurs. As the error messages states, something outside the VM > caused the seg fault. Not exactly, the segfault occurs in a routine outside the VM but it is hard to know what causes the memory corruption. > > good luck. > > peter > > --------------------------------- Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
