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: EOFException
Date Thu, 31 Jan 2013 00:15:48 GMT
Please post your broker config and what URL you're using on the client
side. EOFException in the broker logs usually means the client didn't
disconnect properly


On Wed, Jan 30, 2013 at 5:11 PM, Mohit Anchlia <mohitanchlia@gmail.com>wrote:

> With nio we often see this error even though all MQ servers are up and
> running. We are using 5.7.0. Client then hangs and failover never
> reconnects.
>
> WARN  transport.failover.FailoverTransport [ActiveMQ Transport:  Transport
> (tcp://100.145.3.166:61616) failed, reason:  java.io.EOFException,
> attempting to automatically reconnect
>
> Right after this error I check on netstat and I see TIMED_WAIT as if the
> connection was killed. And after that mq client never reconnects. Is this
> some issue that has been experienced before and the second problem is that
> failover doesn't seem to be working
>



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

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