2012/5/24 David kerber <dcker...@verizon.net>: > Any suggestions as to where to start looking for this error? > > This is TC 7.0.22 32-bit running on Windows Server 2008R2, on a Dell > Dual-processor 4-core hyperthreaded (total 16 cores according to the OS) box > with 16GB RAM. Overall memory usage is approx 26% according to task > Manager. > > There are 5 instances of Tomcat running, each on a different TCP port, and > each running from its own doc base. They are all running the same > application, though with slightly different settings for different > customers. I have allocated 512MB to each instance, and the biggest one is > using approx 260MB according to task manager. Only the single instance of > TC has had this problem, and it has died each of the last two days, after > running perfectly for over two months. All other instances continue to run > with no trouble, including one which has much more activity than the one > with the trouble. > > This is the only unexpected entry in any of the TC logs. > > 2012-05-23 08:12:04 Commons Daemon procrun stdout initialized > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7729e39e, pid=4432, > tid=4588 > # > # JRE version: 6.0_27-b07 > # Java VM: Java HotSpot(TM) Server VM (20.2-b06 mixed mode windows-x86 ) > # Problematic frame: > # C [ntdll.dll+0x2e39e] > # > # An error report file with more information is saved as: > # C:\Windows\system32\hs_err_pid4432.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > > > According to C:\Windows\system32\hs_err_pid4432.log, the problem appears to > be in the sun database access stuff, but I'm not sure if the "thread > blocked" messages in the below listing mean anything. > > And here is C:\Windows\system32\hs_err_pid4432.log. Unfortunately, pasting > it into the e-mail hosed the line wrapping: > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000770e32d0, > pid=1400, tid=5028 > # > # JRE version: 6.0_27-b07 > # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.2-b06 mixed mode > windows-amd64 compressed oops) > # Problematic frame: > # C [ntdll.dll+0x532d0] > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # > > --------------- T H R E A D --------------- > > Current thread (0x000000000cf7b800): JavaThread "http-apr-55001-exec-570" > daemon [_thread_in_vm, id=5028, > stack(0x000000000cb00000,0x000000000cc00000)] > > siginfo: ExceptionCode=0xc0000005, reading address 0x00000e6779be1a38 > > Registers: > RAX=0x0000000007b28890, RBX=0x00000e6779be1a30, RCX=0x000000ffffffffff, > RDX=0x00000000082f11e0 > RSP=0x000000000cbfea10, RBP=0x0000000000000000, RSI=0x0000000000470000, > RDI=0x00000000082f11f0 > R8 =0x00000000082f11f0, R9 =0x0000000000000001, R10=0x000000000000000c, > R11=0x00000000fd3b1748 > R12=0x0000000000000000, R13=0x00000000e3773cb0, R14=0x000000000cbfebf0, > R15=0x000000000cf7b800 > RIP=0x00000000770e32d0, EFLAGS=0x0000000000010206 > > Top of Stack: (sp=0x000000000cbfea10) > 0x000000000cbfea10: 0000000000000000 00000000014e1897 > 0x000000000cbfea20: 0000000000000001 0000000000000001 > 0x000000000cbfea30: 00000000078f29c8 000000006d908410 > 0x000000000cbfea40: 0000000000000004 0000000000000001 > 0x000000000cbfea50: 000000000cf7b800 000000000cbfebf0 > 0x000000000cbfea60: 00000000e3773cb0 0000000000000000 > 0x000000000cbfea70: 0000000000000000 00000000082f11f0 > 0x000000000cbfea80: 000000000cbfebb8 000007fefde510c4 > 0x000000000cbfea90: 00000000e3772f90 000000000cf7b800 > 0x000000000cbfeaa0: 000000000cbfeac8 000000000cbfeb28 > 0x000000000cbfeab0: 000000000cf7b800 000000006d927949 > 0x000000000cbfeac0: 000000000cbfeb28 00000000014d58fa > 0x000000000cbfead0: 0000000007f08120 00000000014d58fa > 0x000000000cbfeae0: 00000000e81708c0 000000006d409fc4 > 0x000000000cbfeaf0: 000000000cf7b9d0 000000000cbfebb8 > 0x000000000cbfeb00: 0000000000000001 0000000007855268 > > Instructions: (pc=0x00000000770e32d0) > 0x00000000770e32b0: ff ff 00 00 00 48 33 de 48 23 c1 48 c1 eb 04 48 > 0x00000000770e32c0: 33 d8 48 33 1d ff f0 0d 00 48 c1 e3 04 0f 0d 0b > 0x00000000770e32d0: 4c 8b 63 08 49 bd 01 00 00 00 01 00 00 00 49 be > 0x00000000770e32e0: ff 7f 00 00 ff ff ff ff c6 42 0f 80 c6 42 0e 00 > > > Register to memory mapping: > > RAX=0x0000000007b28890 is an unknown value > RBX=0x00000e6779be1a30 is an unknown value > RCX=0x000000ffffffffff is an unknown value > RDX=0x00000000082f11e0 is an unknown value > RSP=0x000000000cbfea10 is pointing into the stack for thread: > 0x000000000cf7b800 > RBP=0x0000000000000000 is an unknown value > RSI=0x0000000000470000 is an unknown value > RDI=0x00000000082f11f0 is an unknown value > R8 =0x00000000082f11f0 is an unknown value > R9 =0x0000000000000001 is an unknown value > R10=0x000000000000000c is an unknown value > R11=0x00000000fd3b1748 is an unknown value > R12=0x0000000000000000 is an unknown value > R13=0x00000000e3773cb0 is an oop > {method} > - klass: {other class} > R14=0x000000000cbfebf0 is pointing into the stack for thread: > 0x000000000cf7b800 > R15=0x000000000cf7b800 is a thread > > > Stack: [0x000000000cb00000,0x000000000cc00000], sp=0x000000000cbfea10, > free space=1018k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > C [ntdll.dll+0x532d0] RtlFreeHeap+0xd0 > > [error occurred during error reporting (printing native stack), id > 0xc0000005] >
The above line - so it failed so hard, that was not able to properly report the error? Regarding your question > I'm not sure if the "thread blocked" messages in the below listing mean > anything. I see nothing wrong with Apr connector threads state. They are executing java code. Only several of them are in "_thread_in_native" state. Nothing else can be said, because java stack traces are not present. You can take thread dumps from Tomcat instance when it is running and compare. Note, that this connector using Tomcat-Native library is one more native component in the picture. I have nothing against it, just saying. > each of the last two days Two days ago? http://en.wikipedia.org/wiki/Solar_eclipse_of_May_20,_2012 BTW, there is known stability issue with that version of Tomcat if you have compression="on" on your connector http://issues.apache.org/bugzilla/show_bug.cgi?id=52121 Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
