You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Yuanxianhu (Tiger, Secospace)" <yu...@huawei.com> on 2015/03/02 08:47:59 UTC
Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
Dear:
I use Tomcat NIO to deal with web request, but tomcat crashed frequently because of NIO EXCEPTION_ACCESS_VIOLATION. Attachments are crash logs.
I need you help how to analyze this problem.
Tomcat Version:
Server version: Apache Tomcat/6.0.37
Server built: Apr 29 2013 11:34:47
Server number: 6.0.0.37
OS: Windows NT 6.1 , 64 bit Build 7601 Service Pack 1
JRE version: 6.0_43-b01
Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode windows-amd64 compressed oops)
Crash example:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000776832d0, pid=8488, tid=26852
#
# JRE version: 6.0_43-b01
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 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
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x000000002cd18000): JavaThread "catalina-exec-2165" daemon [_thread_in_native, id=26852, stack(0x0000000019510000,0x0000000019550000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x000002564718be58
Registers:
RAX=0x0000000000007e98, RBX=0x000002564718be50, RCX=0x000000ffffffffff, RDX=0x000000000f23be00
RSP=0x000000001954f5d0, RBP=0x0000000000000000, RSI=0x000000000f1c0000, RDI=0x000000000f23be10
R8 =0x000000000f23be10, R9 =0x00002641003e0001, R10=0x0000000077767c50, R11=0x0000000020d77640
R12=0x0000000000000000, R13=0x0000000095a63420, R14=0x000000001954f750, R15=0x000000002cd18000
RIP=0x00000000776832d0, EFLAGS=0x0000000000010206
Top of Stack: (sp=0x000000001954f5d0)
0x000000001954f5d0: 000000001c12f880 0000000077655472
0x000000001954f5e0: 000000002cd18000 000000001954f750
0x000000001954f5f0: 0000000095a63420 0000000000000000
0x000000001954f600: 0000000000000000 000000001954f6a8
0x000000001954f610: 000000002cd18000 000000001954f750
0x000000001954f620: 0000000095a63420 0000000000000000
0x000000001954f630: 0000000000000000 0000000000000000
0x000000001954f640: 000007fefe2c17c0 000007fefe2c1aa5
0x000000001954f650: 000000000f23be10 000000000f23be10
0x000000001954f660: 000000001c0e6310 000007fefe2ee591
0x000000001954f670: 0000000095a63420 000000002cd181d0
0x000000001954f680: 0000000099633790 000000001954f760
0x000000001954f690: 0000000000002838 000000006d6d37d0
0x000000001954f6a0: 0000000000000000 0000000000000000
0x000000001954f6b0: 0000000000000000 000000000246907c
0x000000001954f6c0: 000000001954f718 000000006dad327a
Instructions: (pc=0x00000000776832d0)
0x00000000776832b0: ff ff 00 00 00 48 33 de 48 23 c1 48 c1 eb 04 48
0x00000000776832c0: 33 d8 48 33 1d ff f0 0d 00 48 c1 e3 04 0f 0d 0b
0x00000000776832d0: 4c 8b 63 08 49 bd 01 00 00 00 01 00 00 00 49 be
0x00000000776832e0: ff 7f 00 00 ff ff ff ff c6 42 0f 80 c6 42 0e 00
Register to memory mapping:
RAX=0x0000000000007e98 is an unknown value
RBX=0x000002564718be50 is an unknown value
RCX=0x000000ffffffffff is an unknown value
RDX=0x000000000f23be00 is an unknown value
RSP=0x000000001954f5d0 is pointing into the stack for thread: 0x000000002cd18000
RBP=0x0000000000000000 is an unknown value
RSI=0x000000000f1c0000 is an unknown value
RDI=0x000000000f23be10 is an unknown value
R8 =0x000000000f23be10 is an unknown value
R9 =0x00002641003e0001 is an unknown value
R10=0x0000000077767c50 is an unknown value
R11=0x0000000020d77640 is an unknown value
R12=0x0000000000000000 is an unknown value
R13=
[error occurred during error reporting (printing register info), id 0xc0000005]
Stack: [0x0000000019510000,0x0000000019550000], sp=0x000000001954f5d0, free space=253k
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]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J sun.nio.ch.SocketDispatcher.close0(Ljava/io/FileDescriptor;)V
J java.nio.channels.spi.AbstractSelectableChannel.implCloseChannel()V
J java.nio.channels.spi.AbstractInterruptibleChannel.close()V
J org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run()V
J java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Ljava/lang/Runnable;)V
J java.util.concurrent.ThreadPoolExecutor$Worker.run()V
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
--------------- S Y S T E M ---------------
OS: Windows NT 6.1 , 64 bit Build 7601 Service Pack 1
CPU:total 24 (6 cores per cpu, 2 threads per core) family 6 model 45 stepping 7, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, ht
Memory: 4k page, physical 16741764k(226832k free), swap 33481684k(12445704k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (20.14-b01) for windows-amd64 JRE (1.6.0_43-b01), built on Mar 1 2013 01:52:33 by "java_re" with MS VC++ 8.0 (VS2005)
time: Thu Feb 26 08:21:14 2015
elapsed time: 87264 seconds
Best Regards
Re: 答复: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
Posted by Mark Thomas <ma...@apache.org>.
On 02/03/2015 09:21, Yuanxianhu (Tiger, Secospace) wrote:
> My friend,
> Can you give me the bug ID for JVM?
To repeat what I said previously.
We can't help. You'll have to speak yo your JVM vendor.
Mark
>
> Best Regards
>
>
>
>
>
> -----邮件原件-----
> 发件人: Mark Thomas [mailto:markt@apache.org]
> 发送时间: 星期一 2015年3月2日 17:20
> 收件人: Tomcat Users List
> 主题: Re: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
>
> On 02/03/2015 07:47, Yuanxianhu (Tiger, Secospace) wrote:
>> Dear:
>>
>> I use Tomcat NIO to deal with web request, but tomcat crashed
>> frequently because of NIO EXCEPTION_ACCESS_VIOLATION. Attachments are
>> crash logs.
>>
>>
>>
>> I need you help how to analyze this problem.
>
> We can't help. That is a JVM bug, not a Tomcat bug.
>
> You'll have to speak yo your JVM vendor.
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
答复: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
Posted by "Yuanxianhu (Tiger, Secospace)" <yu...@huawei.com>.
My friend,
Can you give me the bug ID for JVM?
Best Regards
-----邮件原件-----
发件人: Mark Thomas [mailto:markt@apache.org]
发送时间: 星期一 2015年3月2日 17:20
收件人: Tomcat Users List
主题: Re: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
On 02/03/2015 07:47, Yuanxianhu (Tiger, Secospace) wrote:
> Dear:
>
> I use Tomcat NIO to deal with web request, but tomcat crashed
> frequently because of NIO EXCEPTION_ACCESS_VIOLATION. Attachments are
> crash logs.
>
>
>
> I need you help how to analyze this problem.
We can't help. That is a JVM bug, not a Tomcat bug.
You'll have to speak yo your JVM vendor.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 6.0.37 EXCEPTION_ACCESS_VIOLATION Crash
Posted by Mark Thomas <ma...@apache.org>.
On 02/03/2015 07:47, Yuanxianhu (Tiger, Secospace) wrote:
> Dear:
>
> I use Tomcat NIO to deal with web request, but tomcat crashed
> frequently because of NIO EXCEPTION_ACCESS_VIOLATION. Attachments are
> crash logs.
>
>
>
> I need you help how to analyze this problem.
We can't help. That is a JVM bug, not a Tomcat bug.
You'll have to speak yo your JVM vendor.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org