jrockit崩溃文件,大家看看能看出什么问题吗?

beiai1014 beiai1014 墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年,写一次发全网 我也要 + 加入社区
===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 00:02:25 on Fri Feb 22 17:01:49 2008

Additional information is available in:
E:\wtp\eclipse\jrockit.3792.dump
E:\wtp\eclipse\jrockit.3792.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.

Error Message: No exception handler found [56]
Exception Rec: EXCEPTION_ACCESS_VIOLATION (c0000005) at 0x0097A4F6 - memory at 0x00000000 could not be written.
Minidump : Wrote mdmp. Size is 154MB
SafeDllMode : -1
Fatal Error : Exception handler not found. Thread 28 died abruptly. java/lang/NullPointerException

Version : BEA JRockit(R) R27.4.0-90-89592-1.6.0_02-20070928-1715-windows-ia32
GC Strategy : Mode: throughput. Currently using strategy: genparpar
GC Status : OC is not running. Last finished OC was OC#1.
: YC is not running. Last finished YC was YC#8.
OC History : Strategy genparpar was used for OC#1.
YC History : Ran 8 YCs before OC#1.
: Ran 0 YCs since last OC.
Heap : 0x00D00000 - 0x04D00000
Compaction : 0x04900000 - 0x04D00000
NurseryList : 0x00D06E60 - 0x03675290
KeepArea : 0x01D04020 - 0x024FFFE8
NurseryMarker: [ 0x024FFFE8, 0x0295F3A0 ]
CompRefs : References are 32-bit.
CPU : Intel SSE SSE2 SSE3
Number CPUs : 2
Tot Phys Mem : 1064677376 (1015 MB)
OS version : Microsoft Windows XP version 5.1 Service Pack 2 (Build 2600) (32-bit)
Thread System: Windows Threads
Java locking : Normal
State : JVM is running
Command Line : -Dcatalina.base=E:\webObj\.metadata\.plugins\org.eclipse.wst.server.core\tmp0 -Dcatalina.home=C:\Tomcat -Dwtp.deploy=E:\webObj\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps -Djava.endorsed.dirs=C:\Tomcat\common\endorsed -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:4220 -Dsun.java.launcher=SUN_STANDARD org.apache.catalina.startup.Bootstrap start
java.home : C:\jrockit-R27.4.0-jdk1.6.0_02\jre
j.class.path : C:\Tomcat\bin\bootstrap.jar;C:\jrockit-R27.4.0-jdk1.6.0_02\lib\tools.jar
j.lib.path : C:\jrockit-R27.4.0-jdk1.6.0_02\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin;C:\jdk1.5\bin\..\jre\bin\client;C:\jdk1.5\bin\..\jre\bin;C:\jdk1.5\bin;D:\mysql\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
JAVA_HOME : C:\jdk1.5
_JAVA_OPTIONS: <not set>
PATH : C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin;C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin;C:\jdk1.5\bin\..\jre\bin\client;C:\jdk1.5\bin\..\jre\bin;C:\jdk1.5\bin;D:\mysql\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
C Heap : Good; no memory allocations have failed
StackOverFlow: 0 StackOverFlowErrors have occured
OutOfMemory : 0 OutOfMemoryErrors have occured

Registers (from ThreadContext: 0x3223EA48 / OS context: 0x3223F270):
eax = 00000055 ecx = 0000b481 edx = 00b62144 ebx = 3223f580
esp = 3223f53c ebp = 319b4f78 esi = 00000038 edi = 00b169b8
es = 00000023 cs = 0000001b ss = 00000023 ds = 00000023
fs = 0000003b gs = 00000000
eip = 0097a4f6 eflags = 00010202

Stack:
(* marks the word pointed to by the stack pointer)
3223f53c: 0000003f* 00000e30 319b4ea8 00af9ff9 00000038 00b169b8
3223f554: 3223f580 307bc5b0 319b4ea8 3223f620 00afa014 00000038
3223f56c: 00b169b8 3223f580 0098657a 00000038 00b169b8 00000028
3223f584: 307634e0 307bc5b0 319b4ea8 319b4ff8 00000000 00000000

Code:
(* marks the word pointed to by the instruction pointer)
0097a4c4: 548bc085 15890c24 00b61ce8 4c8b1874 50511424 00020068
0097a4dc: 20f06800 59e800b6 830017f0 3f6a10c4 22f005c7 000100b6
0097a4f4: 05c70000* 00000000 00001267 17fa9be8 cccccc00 cccccccc
0097a50c: cccccccc 0080ec81 c0330000 24448956 24448918 6850501c

Loaded modules:
(* denotes the module causing the exception)
00400000-00411fff C:\jrockit-R27.4.0-jdk1.6.0_02\bin\javaw.exe
7c920000-7c9b3fff C:\WINDOWS\system32\ntdll.dll
7c800000-7c91cfff C:\WINDOWS\system32\kernel32.dll
77d10000-77d9efff C:\WINDOWS\system32\USER32.dll
77ef0000-77f36fff C:\WINDOWS\system32\GDI32.dll
77da0000-77e48fff C:\WINDOWS\system32\ADVAPI32.dll
77e50000-77ee1fff C:\WINDOWS\system32\RPCRT4.dll
77fc0000-77fd0fff C:\WINDOWS\system32\Secur32.dll
77be0000-77c37fff C:\WINDOWS\system32\MSVCRT.dll
76300000-7631cfff C:\WINDOWS\system32\IMM32.DLL
62c20000-62c28fff C:\WINDOWS\system32\LPK.DLL
73fa0000-7400afff C:\WINDOWS\system32\USP10.dll
7c340000-7c395fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\msvcr71.dll
00930000-00bcbfff *C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\jrockit\jvm.dll
76b10000-76b39fff C:\WINDOWS\system32\WINMM.dll
71a20000-71a36fff C:\WINDOWS\system32\WS2_32.dll
71a10000-71a17fff C:\WINDOWS\system32\WS2HELP.dll
6d4b0000-6d4d8fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\jdwp.dll
6d770000-6d775fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\npt.dll
6d820000-6d82bfff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\verify.dll
6d460000-6d47efff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\java.dll
6d3c0000-6d3c7fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\hpi.dll
6d860000-6d86efff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\zip.dll
6d330000-6d336fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\dt_socket.dll
719c0000-719fdfff C:\WINDOWS\System32\mswsock.dll
323c0000-323e6fff C:\WINDOWS\system32\DNSAPI.dll
323f0000-32407fff D:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 7.0\dnsq.dll
77f40000-77fb5fff C:\WINDOWS\system32\SHLWAPI.dll
32480000-32487fff C:\WINDOWS\System32\winrnr.dll
32490000-324bbfff C:\WINDOWS\system32\WLDAP32.dll
324d0000-324d5fff C:\WINDOWS\system32\rasadhlp.dll
60fd0000-61024fff C:\WINDOWS\system32\hnetcfg.dll
71a00000-71a07fff C:\WINDOWS\System32\wshtcpip.dll
6d620000-6d632fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\net.dll
76bc0000-76bcafff C:\WINDOWS\system32\psapi.dll
31a50000-31a77fff C:\WINDOWS\system32\rsaenh.dll
759d0000-75a7dfff C:\WINDOWS\system32\USERENV.dll
5fdd0000-5fe23fff C:\WINDOWS\system32\netapi32.dll
36570000-36682fff C:\jrockit-R27.4.0-jdk1.6.0_02\jre\bin\dbghelp.dll


"Finalizer" id=8 idx=0x28 tid=4816 lastJavaFrame=0x3223F768

Stack 0: start=0x32200000, end=0x32240000, guards=0x32203000 (ok), forbidden=0x32201000
Thread Stack Trace:
at _dumpForceDump+118()@0x0097A4F6
at _vmFatalErrorMsgV+73()@0x00AF9FF9
at _vmFatalErrorMsg+20()@0x00AFA014
at _excThrowPendingException+762()@0x0098657A
at _excThrowPendingException+1195()@0x0098672B
at _excCheckUnprocessedException+248()@0x00986898
at _tsCheckTransitToJava+30()@0x009883EE
at _nativeUnlock+62()@0x00A6C48E
at _bpDispatchBreakpoint+88()@0x00946BD8
at _trapiTryHandleBreakpoint+17()@0x00AEA6F1
at _trapiTryHandleIllegalInstruction+12()@0x00AEB3EC
at _trapGetStackOverFlowCount+309()@0x00AEA905
at _except_handler3+97()@0x7C34246E
at RtlConvertUlongToLargeInteger+122()@0x7C9237BF
at RtlConvertUlongToLargeInteger+70()@0x7C92378B
at KiUserExceptionDispatcher+14()@0x7C92EAFA
at ZwContinue+12()@0x7C92D625
-- Java stack --
at jrockit/vm/ExceptionHandler.throwPendingType()V(Native Method)
at jrockit/vm/RNI.callMarker()V(RNI.java)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
...全文

相关推荐

JRockit Mission Control介绍及配置

JRockit Memory Leak Detector 提供了一种有效的方法来识别和解决这类问题,防止因内存泄漏导致的系统性能下降甚至崩溃。

sunnyhgj

使用JRockit检测和解决内存泄漏问题

通过安装和配置JRockit,运行应用程序,并使用JRockit Mission Control等工具进行分析,开发人员可以定位和修复潜在的内存泄漏问题。在Mission Control的内存分析工具中,您可以查看对象的引用链和对象的生命周期。您可以使用内存分析工具来查看应用程序的内存使用情况,并检查是否存在内存泄漏。现在,您可以运行您的Java应用程序,并让其在JRockit虚拟机上执行。通过使用JRockit进行内存泄漏检测,您可以发现这个问题并采取适当的措施来修复它。步骤五:定位和修复内存泄漏。

代码创造者

JRockit JAVA内存溢出检测的使用(CHM)

**JRockit JAVA内存溢出检测的使用**Java内存溢出是开发和运行Java应用程序时常见的问题,可能导致程序崩溃或性能急剧下降。

weixin_38669628

JRockit+Mission+Control

#### BEA JRockit Mission Control:内存泄漏的终极解决方案面对内存泄漏这一棘手问题,BEA公司(现已被Oracle收购)推出了JRockit Mission Control

hujd20030325

Jrockit Mission Control

异常信息** - JRA 还能够捕获并记录异常信息,这对于调试异常导致的应用崩溃等问题非常有帮助。**8.

J2EE_BI
评论 5
收藏 已收藏
分享
返回顶部
beiai1014
Java SE 62,620 成员 307,251 内容