James,
We have a similar issue under different circumstances.
When we bounce our server which is using spring 2 to produce and consume
messages on a failover queue, we sometimes get a runaway log file due to the
process not shutting down correctly within tomcat.
We then get within seconds, mb's of log saying:
org.apache.activemq.transport.failover.FailoverTransport - Transport failed,
attempting to automatically reconnect due to: java.io.IOException
java.io.IOException
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:37)
at
org.apache.activemq.state.ConnectionStateTracker.track(ConnectionStateTracker.java:94)
at
org.apache.activemq.transport.failover.FailoverTransport.oneway(FailoverTransport.java:383)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:43)
at
org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:69)
at
org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:74)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1171)
at
org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:1660)
at
org.apache.activemq.ActiveMQMessageConsumer.close(ActiveMQMessageConsumer.java:541)
at
org.springframework.jms.support.JmsUtils.closeMessageConsumer(JmsUtils.java:144)
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.clearResources(DefaultMessageListenerContainer.java:899)
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:865)
at java.lang.Thread.run(Thread.java:595)
dkfn wrote:
>
> Thanks James,
>
> I moved away from failover:tcp://localhost:61616 for reasons that now
> completely escape me. I'll put that back in and see the problem goes
> away.
>
> cheers,
> j.
>
> On 3/5/07, James Strachan <[EMAIL PROTECTED]> wrote:
>> On 3/5/07, Jamie McCrindle <[EMAIL PROTECTED]> wrote:
>> > Hi all,
>> >
>> > I keep getting the following exception at what appear to be random
>> intervals:
>> >
>> > 2007-03-05 14:42:40,367 INFO [ActiveMQ Transport: tcp://localhost/1
>> > 27.0.0.1:51515] FailoverTransport.handleTransportFailure | Transport
>> failed, att
>> > empting to automatically reconnect due to: java.io.EOFException
>> > java.io.EOFException
>> > at java.io.DataInputStream.readInt(DataInputStream.java:358)
>> > at
>> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.
>> > java:267)
>> > at
>> org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTranspo
>> > rt.java:156)
>> > at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:
>> > 136)
>> > at java.lang.Thread.run(Thread.java:595)
>> >
>> > Any ideas? It doesn't appear to be affecting the messaging...
>> >
>> > I'm using:
>> >
>> > ActiveMQ 4.1.0 and a broker url of: tcp://localhost:61616
>> >
>> > activemq.conf is the standard one out of the 4.1 distro.
>>
>> It typically just means that the socket has closed while the async
>> reading thread is trying to read from the socket. It can generally be
>> ignored. If you were using a URL of failover:tcp://localhost:61616
>> then the transport would automatically reconnect under the covers for
>> you. If you're not using failover then maybe you're closing
>> connections?
>>
>> --
>>
>> James
>> -------
>> http://radio.weblogs.com/0112098/
>>
>
>
--
View this message in context:
http://www.nabble.com/Transport-failed%2C-attempting-to-automatically-reconnect-due-to%3A-java.io.EOFException-tf3349326s2354.html#a11610082
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
