activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://broker#56570) disposed.
Date Mon, 04 Mar 2013 20:46:38 GMT
Looks like the client side transport is considered disposed when the broker
is trying to send it a message after connection.close() has been initiated.
What version are you using?


On Mon, Mar 4, 2013 at 12:35 PM, Sune Vuorela <nospam@vuorela.dk> wrote:

> Hi friendly people
>
> I'm quite happily using ActiveMQ in a corner of a project and is
> regrettinrg I didn't learn about it earlier.
>
> Unfortuanately I from time to time get a WARN entry in my log from
> ActiveMQ and I'm not sure I fully understand the meaning of it and the
> importance.
>
> I hope someone can enlighten me a bit about it.
>
> The log entry is:
>
>  [Async Exception Handler] WARN
>  org.apache.activemq.broker.TransportConnection.Transport
>  (TransportConnection.java:205) - Transport Connection to:
>  vm://broker#56570 failed:
>  org.apache.activemq.transport.TransportDisposedIOException: Peer
>  (vm://broker#56570) disposed.
>
>
> and if run with DEBUG enabled, it is: (numbers are different)
>
> [Async Exception Handler] DEBUG
> org.apache.activemq.broker.TransportConnection.Transport
> (TransportConnection.java:203) - Transport Connection to:
> vm://broker#11424 failed:
> org.apache.activemq.transport.TransportDisposedI
> OException: Peer (vm://broker#11424) disposed.
> org.apache.activemq.transport.TransportDisposedIOException: Peer
> (vm://broker#11424) disposed.
>  at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:89)
>  at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68)
>  at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
>  at
> org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1312)
>  at
> org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:838)
>  at
> org.apache.activemq.broker.TransportConnection.dispatchSync(TransportConnection.java:799)
>  at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:154)
>  at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
>  at
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
>  at org.apache.activemq.transport.vm.VMTransport.stop(VMTransport.java:199)
>  at
> org.apache.activemq.transport.vm.VMTransportServer$1.stop(VMTransportServer.java:79)
>  at
> org.apache.activemq.transport.TransportFilter.stop(TransportFilter.java:65)
>  at
> org.apache.activemq.transport.TransportFilter.stop(TransportFilter.java:65)
>  at
> org.apache.activemq.transport.ResponseCorrelator.stop(ResponseCorrelator.java:132)
>  at org.apache.activemq.util.ServiceSupport.dispose(ServiceSupport.java:43)
>  at
> org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:701)
>  at ....my code calling connection.close()
>
> AMQ isn't processing many messages, and I do see this 2-3 times pr week.
>
> So, what does this mean?
>
> THanks in advance
>
> /Sune
>
>


-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message