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
It's more than cosmetic, since it keeps the connection alive, preventing the
connection pool's default idle timeout from triggering after 30seconds and
breaking the connection primaturely. The TcpTransport uses an
InactivityMonitor which keeps connections alive, and so you don't want the
connecti
Jason Rosenberg wrote:
>
> Don't know if you are using connection poolingI've solved this issue
> by setting the idle timeout to 0 (infinite timeout), for pooled
> connections.Unfortunately, the PooledConnectionFactory doesn't expose
> the idleTimeout property, so I sub-classed it as a w
Hi,
Don't know if you are using connection poolingI've solved this issue by
setting the idle timeout to 0 (infinite timeout), for pooled
connections.Unfortunately, the PooledConnectionFactory doesn't expose
the idleTimeout property, so I sub-classed it as a work-around. I've filed
an iss
Please have a look at this urgent and critical issue which is still open
we are using activemq-all-5.0.0.jar
--
View this message in context:
http://www.nabble.com/Transport-failed%2C-attempting-to-automatically-reconnect-due-to...-tp15159638s2354p15306655.html
Sent from the ActiveMQ - User m
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
12 matches
Mail list logo
