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 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. good luck. peter
jean-frederic clere <[EMAIL PROTECTED]> wrote: Clere, Jean-Frederic wrote: > Jeff Rogers wrote: > >> Hello, >> >> I hate to post this to the dev list, but we need consulting help. I >> have no idea where to look for reputable Tomcat consulting. >> >> We are at our wits end and ready to make the jump to commercial >> software due to a "signal 11" crashing problem with our Tomcat servers. > > > "signal 11" are normaly problems in the JVM's. Which java version are > you using? BTW: I have tried to "overload" TC and I have got: ++++ An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0x40098aa6 Function name=malloc Library=/lib/libc.so.6 Current Java thread: at java.net.SocketInputStream.socketRead(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:85) at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:767) at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:428) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:569) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java +++ That is with JVM 1.3.1_03... and 4.1.24. --------------------------------- Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard
