-
1. Re: Message Consumer becomes passive
tonytam Feb 19, 2009 3:56 PM (in response to tonytam)I can see channel becomes inactive and consumers are getting closed in logs
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:41214
at org.apache.activemq.transport.InactivityMonitor$4.run(InactivityMonitor.java:164)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2009-02-19 12:21:34,236 DEBUG TransportConnection - Stopping connection: /127.0.0.1:41214
2009-02-19 12:21:34,236 DEBUG TcpTransport - Stopping transport tcp:///127.0.0.1:41214
2009-02-19 12:21:34,237 DEBUG TransportConnection - Stopped transport: /127.0.0.1:41214
2009-02-19 12:21:34,238 DEBUG TransportConnection - Cleaning up connection resources: /127.0.0.1:41214
2009-02-19 12:21:34,238 DEBUG AbstractRegion - Removing consumer: ID:m1.testqa.thinkpassenger.com-33028-1235074593699-0:22:1:1
2009-02-19 12:21:34,238 [127.0.0.1:41214
org.apache.activemq.transport.InactivityIOException: Channel was inactive for too long
-
activemqlog.rar 136.4 KB
-
-
2. Re: Message Consumer becomes passive
martinmurphy Feb 24, 2009 5:46 AM (in response to tonytam)Can you try and disable inactivity monitoring and see if that helps:
tcp://localhost:61616?wireformat.maxInactivityDuration=0
The property is described in the documentation here