异常的javax.jms.JMSException:对等对象已处置 [英] Erratic javax.jms.JMSException: Peer disposed

查看:1024
本文介绍了异常的javax.jms.JMSException:对等对象已处置的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对Java JMS有一个不稳定的问题. 暂时可以正常工作,但是会不正常地抛出以下异常并减少执行.

I have a erratic problem with Java JMS. For moments works fine, but throws the following exception erratically and cut the execution.

重要的是要注意,这是在不停止经纪人的情况下发生的.

It is important to note that this occurs without stopping the broker.

javax.jms.JMSException: Peer (vm://test#1) disposed.
        at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:49)
        at org.apache.activemq.ActiveMQConnection.onAsyncException(ActiveMQConnection.java:1773)
        at org.apache.activemq.ActiveMQConnection.onException(ActiveMQConnection.java:1790)
        at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
        at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:114)
        at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:99)
        at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:203)
        at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122)
        at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://test#1) disposed.

推荐答案

我认为ActiveMQ可能是 问题:

I think it could be this issue with ActiveMQ: https://issues.apache.org/jira/browse/AMQ-2902

此问题跟踪程序线程说它是无害的(这只是一个嘈杂的INFO级别日志消息),并且已在ActiveMQ 5.4.2中修复.

This issue tracker thread says that it is harmless (it is just a noisy INFO level log message), and that it is fixed in ActiveMQ 5.4.2.

另一方面,您说异常削减执行力" ... ... 可能表示这与您的问题不同...

On the other hand, you say that the exception "cut the execution" ... which could mean that this is a different issue to yours ...

更新

任何人都无法通过升级ActiveMQ来解决同行处置"异常,并且该异常与关机无关(请参阅无法关机使用内置的BrokerService.stop调用的嵌入式activeMQ服务)应考虑提供错误报告.

Anyone getting a "peer disposed" exception that isn't fixed by upgrading ActiveMQ, and isn't related to shutdown (see Unable to shutdown embedded activeMQ service using the built in BrokerService.stop call) should consider lodging a bug report.

这篇关于异常的javax.jms.JMSException:对等对象已处置的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆