-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Taylan,
On 3/30/2010 5:51 AM, Taylan Develioglu wrote: > We're still having some crashes (segfaults), they may or not be related > to the previous ones. :( > It seems libapr had something to do with it. [snip] > # Problematic frame: > # C [libapr-1.so.0+0x1c0a0] [snip] > Stack: [0x0000000041d86000,0x0000000041da7000], sp=0x0000000041da57d0, > free space=7d0000000000000018k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, > C=native code) > C [libapr-1.so.0+0x1c0a0] > > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.apache.tomcat.jni.Socket.accept(J)J+0 So, this happens in APR's Socket.accept method? I suspect that if something were wrong in that method, it would be apparent to roughly 50% of the world's web servers. Do you have large electromagnetic flux sources anywhere near your servers? Your problems just don't seem to make any kind of sense whatsoever. Can you bring a server to your home and hit it with JMeter for a week or so and see if you can get it to crash? Maybe you have toxic mold in your rack and the JVM is trying to commit suicide to put itself out of its misery... - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuzqPgACgkQ9CaO5/Lv0PD7rgCcDWhOzY93YAxoRcGvoXcx9awM TbYAoIP641cecvi4SVpaW1ZW4nWnP/gS =IV6q -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
