Details of the inactivity monitor are at
http://activemq.apache.org/activemq-inactivitymonitor.html. It's on by
default, so if you haven't modified any settings related to it, it should
be working correctly.
An EOFException typically means that something closed the TCP connection.
Often it's the p
I have not configured any inactivity monitoring. How can I check if any
exists by default?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Transport-failed-attempting-to-automatically-reconnect-due-to-java-io-EOFException-tp2351687p4728568.html
Sent from the ActiveMQ - Us
Are you using the inactivity monitor on the connection?
On Jul 14, 2017 2:54 AM, "akpuvvada" wrote:
> We are also facing the same issue.
> I have two Active MQ Brokers on different machine configured as configured
> as Master/Slave using shared store.
> We are suing the current release version.
We are also facing the same issue.
I have two Active MQ Brokers on different machine configured as configured
as Master/Slave using shared store.
We are suing the current release version.
Transport (tcp://localhost:61616) failed , attempting to automatically
reconnect: java.io.EOFException
y configuration) or should I stop using 5.0?
>>
>> Thanks for any suggestions!
>>
>> /Ur
>>
>>
>> [ActiveMQ Transport: tcp:///10.1.1.134:61616] 2008-03-15 21:53:20,786
>> [WARN ,FailoverTransport 236] Transport failed, attempting to
>> automaticall
veMQ Transport: tcp:///10.1.1.134:61616] 2008-03-15 21:53:20,786
> [WARN ,FailoverTransport 236] Transport failed, attempting to
> automatically reconnect due to: java.io.EOFException
> java.io.EOFException
> at java.io.DataInputStream.readInt(DataInputStream.java:375)
>
using 5.0.0. Is there a simple solution to this
(in my configuration) or should I stop using 5.0?
Thanks for any suggestions!
/Ur
[ActiveMQ Transport: tcp:///10.1.1.134:61616] 2008-03-15 21:53:20,786 [WARN
,FailoverTransport 236] Transport failed, attempting to automatically reconnect
d
We are using the failover transport, but still are getting the same
exception, but in a different place (see stack trace):
org.apache.activemq.transport.failover.FailoverTransport Transport failed,
attempting to automatically reconnect due to: java.io.EOFException
java.io.EOFException
at
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 o
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 k
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
emptin
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.EOFExcepti
12 matches
Mail list logo
