Tomcat itself can't create a sig 11. The only ways a sig 11 can happen are errors in the jvm or in a native library. Tomcat has no native library, so typical sources for this kind of trouble are the vm, the native libraries of the jdk or the native libraries of third party extension (like native jdbc drivers).
You should at least provide following info's - tomcat version - If you run tomcat behind a webserver - which one (version) - which connector do you use - vm version (result of java -version) May be the core file contains some information to identify what caused the signal. > -----Urspr�ngliche Nachricht----- > Von: Rob Helmer [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 3. Juli 2002 02:58 > An: [EMAIL PROTECTED] > Betreff: 64bit Java 1.4 on Solaris > > I am trying to run 64-bit Java 1.4 w/ Tomcat, and I get a sig > 11 everytime > I start up with -d64, -server or both. > > -client works, without -d64 works. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
