gpt4 book ai didi

Java 6 JVM 挂起

转载 作者:搜寻专家 更新时间:2023-11-01 03:15:07 25 4
gpt4 key购买 nike

很抱歉发了这么长的帖子,但我想知道在我向 Sun 提交错误报告之前我是否可以得到更多的关注。

JVM:6u11
操作系统:Windows XP SP3
硬件:AMD Athlon 64 X2 4600+ @ 2.41GHz,3.25 GB 内存。

我相信我在 JVM 中遇到了一个错误,即没有为线程提供监视器。在以下线程跟踪中,监视器 <0x12a8f9f8>RelayedMessages-0000000001 收购,最终等待它;随后通知了该线程。然而,即使列出的所有线程都在争夺监视器,但没有一个得到它。

我保证每个引用监视器的线程的线程转储都是完整的 <0x12a8f9f8> .转储是使用 Java VisualVM 获取的,在 16 小时内获取了 3 次,并且每次都显示一致(这些线程未更改)。

有人不同意我的评估,即 JVM 未能将监视器交付给任何符合条件的线程,而它应该交付给其中一个线程吗?

"RelayedMessages-0000000001" daemon prio=6 tid=0x03694400 nid=0x1750 waiting for monitor entry [0x05e1f000..0x05e1fc94]
java.lang.Thread.State: BLOCKED (on object monitor)
at java.lang.Object.wait(Native Method)
at com.companyremoved.thd.EzWaiter.ezWait(EzWaiter.java:249)
- locked <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.waitWithinMessage(IsolatedObject.java:352)
- locked <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.system.coms.ComsSender.waitForAvailablePipe(ComsSender.java:219)
at com.companyremoved.system.coms.ComsSender.sendObject(ComsSender.java:185)
at com.companyremoved.system.coms.ComsSender.processIocMessage(ComsSender.java:98)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:311)
- locked <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.iocMessage(IsolatedObject.java:265)
at com.companyremoved.ioc.IocTarget.iocMessage(IocTarget.java:138)
at com.companyremoved.ioc.IocBinding.iocMessage(IocBinding.java:105)
at com.companyremoved.system.coms.ComsSender$Messages.sendObject(ComsSender.java:333)
at com.companyremoved.system.coms.ComsSender$Messages.sendObject(ComsSender.java:316)
at com.companyremoved.system.coms.RelayedMessage.run(RelayedMessage.java:104)
- locked <0x130fe8e0> (a com.companyremoved.system.coms.RelayedMessage)
at com.companyremoved.thd.RunQueue.runEntry(RunQueue.java:293)
at com.companyremoved.thd.RunQueue.run(RunQueue.java:273)
at java.lang.Thread.run(Unknown Source)

Locked ownable synchronizers:
- None

"ScbPipe Writer" daemon prio=6 tid=0x4fff0c00 nid=0xf14 waiting for monitor entry [0x0594f000..0x0594fc14]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:293)
- waiting to lock <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.iocMessage(IsolatedObject.java:265)
at com.companyremoved.ioc.IocTarget.iocMessage(IocTarget.java:138)
at com.companyremoved.coms.stm.ioc.ComsPipe$Receiver.scbPipeDefaultProcessor(ComsPipe.java:403)
at com.companyremoved.scb.ScbPipe.processObject(ScbPipe.java:915)
- locked <0x131a4ea0> (a java.lang.Object)
at com.companyremoved.scb.ScbPipe.writerRun(ScbPipe.java:817)
at com.companyremoved.scb.ScbPipe.run(ScbPipe.java:728)
at java.lang.Thread.run(Unknown Source)

Locked ownable synchronizers:
- None

"ScbPipe Writer" daemon prio=6 tid=0x4c647400 nid=0xe00 waiting for monitor entry [0x059ef000..0x059efb94]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:293)
- waiting to lock <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.iocMessage(IsolatedObject.java:265)
at com.companyremoved.ioc.IocTarget.iocMessage(IocTarget.java:138)
at com.companyremoved.coms.stm.ioc.ComsPipe$Receiver.scbPipeDefaultProcessor(ComsPipe.java:403)
at com.companyremoved.scb.ScbPipe.processObject(ScbPipe.java:915)
- locked <0x13188bb8> (a java.lang.Object)
at com.companyremoved.scb.ScbPipe.writerRun(ScbPipe.java:817)
at com.companyremoved.scb.ScbPipe.run(ScbPipe.java:728)
at java.lang.Thread.run(Unknown Source)

Locked ownable synchronizers:
- None

"ScbPipe Writer" daemon prio=6 tid=0x035f7800 nid=0x1130 waiting for monitor entry [0x0726f000..0x0726fc94]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:293)
- waiting to lock <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.iocMessage(IsolatedObject.java:265)
at com.companyremoved.ioc.IocTarget.iocMessage(IocTarget.java:138)
at com.companyremoved.coms.stm.ioc.ComsPipe$Receiver.scbPipeDefaultProcessor(ComsPipe.java:403)
at com.companyremoved.scb.ScbPipe.processObject(ScbPipe.java:915)
- locked <0x12a8a478> (a java.lang.Object)
at com.companyremoved.scb.ScbPipe.writerRun(ScbPipe.java:817)
at com.companyremoved.scb.ScbPipe.run(ScbPipe.java:728)
at java.lang.Thread.run(Unknown Source)

Locked ownable synchronizers:
- None

"IOC Signals-0000000001" daemon prio=6 tid=0x03673000 nid=0x1434 waiting for monitor entry [0x0415f000..0x0415fd94]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:293)
- waiting to lock <0x12a8f9f8> (a com.companyremoved.system.coms.ComsSender)
at com.companyremoved.ioc.IsolatedObject.iocMessage(IsolatedObject.java:265)
at com.companyremoved.ioc.IocTarget.iocMessage(IocTarget.java:138)
at com.companyremoved.ioc.IocBinding.iocMessage(IocBinding.java:105)
at com.companyremoved.system.coms.ComsSender$Messages.removePipe(ComsSender.java:302)
at com.companyremoved.system.coms.ConnectionController.disconnect(ConnectionController.java:712)
at com.companyremoved.system.coms.ConnectionController.shutdown(ConnectionController.java:224)
at com.companyremoved.system.coms.ConnectionController.processIocMessage(ConnectionController.java:168)
at com.companyremoved.ioc.IsolatedObject.deliver(IsolatedObject.java:311)
- locked <0x12a8b798> (a com.companyremoved.system.coms.ConnectionController)
at com.companyremoved.ioc.IsolatedObject.access$100(IsolatedObject.java:36)
at com.companyremoved.ioc.IsolatedObject$SignalProxy.run(IsolatedObject.java:526)
at com.companyremoved.thd.RunQueue.runEntry(RunQueue.java:293)
at com.companyremoved.thd.RunQueue.run(RunQueue.java:273)
at java.lang.Thread.run(Unknown Source)

Locked ownable synchronizers:
- None

最佳答案

所提供的线程跟踪对于所讨论的锁是完整的。与我一起工作的另外两个人同意 JVM 错误被明确指出,jProfiler (ej-technologies) 的程序员也是如此。

关于Java 6 JVM 挂起,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/370710/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com