Since recent Windows patches perhaps in combination with Tomcat 7.0.41 and Java 1.7.0_45 patches, our Tomcat instance is crashing once per week or more, 3 times so far in the past 2 weeks, each time generating a similar Windows mdmp file the size of JVM memory and stack trace to ntdll!ZwGetContextThread+0xa. I'm not sure if this is really a JVM or tcnative issue so I'm posting to both Oracle/Java and Apache/Tomcat in case anyone has similar problems. Debug session time: Tue Nov 19 08:48:46.000 2013 (UTC - 5:00) System Uptime: 2 days 3:05:00.493 Process Uptime: 0 days 0:00:26.000 ............................................................ This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (510.96c): Access violation - code c0000005 (first/second chance not available) *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - ntdll!ZwGetContextThread+0xa: 00000000`77271f8a c3 ret Noted in the Stack Trace: ntdll!ZwGetContextThread+0xa ntdll!RtlFindActivationContextSectionString+0x1d6 Environment: Tomcat version 7.0.47 java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) Windows 2008 R2 Standard Build 7601 Intel Xeon CPU E5405 2 GHz 2 CPU x 4 cores each
Other notes from Tomcat startup: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
There is not enough information in your report to diagnose the issue. There is no Tomcat code amongst the only two lines of a stacktrace that you are citing.
I'll try to find out how to bind Java and/or Tomcat APR symbol files into WinDbg.exe ... does anyone have any hints on that?
Here is some further information from a similar crash dump. SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: tcnative_1!Java_org_apache_tomcat_jni_Poll_poll+223 MODULE_NAME: tcnative_1 IMAGE_NAME: tcnative-1.dll DEBUG_FLR_IMAGE_TIMESTAMP: 53467783 STACK_COMMAND: ~83s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_POINTER_READ_BEFORE_WRITE_c0000005_tcnative-1.dll!Java_org_apache_tomcat_jni_Poll_poll BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_BEFORE_WRITE_tcnative_1!Java_org_apache_tomcat_jni_Poll_poll+223 ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:null_pointer_read_before_write_c0000005_tcnative-1.dll!java_org_apache_tomcat_jni_poll_poll FAILURE_ID_HASH: {3d0ef292-369d-05ca-f03e-33ba41a5100c}
As far as I can tell from the provided information, this is a duplicate. If you still see this issue (or something like it) with the latest stable 1.2.x release and the latest stable release of a supported Tomcat version, please open a new bug. What we really need are steps to reproduce. Even if it doesn't reproduce reliable, a script that will trigger then problem (the quicker the better) is very helpful. *** This bug has been marked as a duplicate of bug 56313 ***