Hmm, the inactivity timer is closing the connection: 2014-07-25 17:37:52,373 | DEBUG | Transport Connection to: tcp://[IP ADDRESS]:4507 failed: org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://[IP ADDRESS]:4507 | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ InactivityMonitor Worker org.apache.activemq.transport.InactivityIOException: Channel was inactive for too (>30000) long: tcp://v:4507 at org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) 2014-07-25 17:37:52,374 | DEBUG | Unregistering MBean org.apache.activemq:type=Broker,brokerName=serverABroker,connector=clientConnectors,connectorName=[Connector Name],connectionViewType=clientId,connectionName=queue_1_inbound | org.apache.activemq.broker.jmx.ManagementContext | ActiveMQ InactivityMonitor Worker
Let me ask straight-out - does this cause a a problem for the application? Or, are these log messages and brief interruptions to flow the only real concern? I'm trying to make sure I'm trying to solve the right problem. -- View this message in context: http://activemq.2283324.n4.nabble.com/JMS-to-JMS-Bridge-Connection-tp4684129p4684140.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
