tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Recent tcnative null-dereference with 8.0.0-RC3 and 7.0.45 [tcnative-1.dll+0x7e23]
Date Fri, 27 Sep 2013 23:49:46 GMT
All,

I know Mark and Rainer are working on trying to avoid corruption of what
looks like pollset counts or whatever, but I wanted to know if anyone
can help me decode the cause of the null-dereference that's occurring.

Obviously bandaging the symptom is not the best solution, but keeping
the JVM up and running is a nice feature to have and, since I have no
understanding of APR polling, I can at least modify tcnative to throw an
exception instead of bombing the JVM.

I can't seem to reproduce the problem using an APR connector on Linux:
reports seems to indicate that trivially accessing Tomcat via an HTTP
APR connector will cause a crash, and I was able to run the following
command without bringing down my instance:

$ ab -n 10000 -c 50 http://localhost:28215/my-webapp/index.html

... where localhost:28215 is bound to an
org.apache.coyote.http11.Http11AprProtocol connector.

So, I need help decoding the tcnative-1.dll+0x7e23 pointer, which is
obviously a code pointer, but I have no idea how far into tcnative.dll
0x7e23 points. It's obviously in ..._jni_Poll_poll() but I'm not sure
which pointer is likely to be null.

Can anyone point me in the right direction?

Thanks,
-chris


Mime
View raw message