Hi Darren, inactivity monitor work by sending "keep alive" commands between client and the broker to detect inactive connection. So this exception means that your connection becomes unstable for some reason and that's why it gets closed.
btw. if you use maxInactivityDuration=0 it should turn off inactivity monitor, but from your log it doesn't seems so. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Jun 22, 2011 at 2:46 AM, Darren Govoni <dar...@ontrenet.com> wrote: > Hi, > I am using 5.5.0. When running on 64bit ubuntu on EC2, I have 30 > connections via pyactivemq on same host. They connect fine. get messages. > > Shortly later (like couple minutes) all the connections disappear with this > exception in the activemq log (many of them). > > 2011-06-22 00:36:10,394 | INFO | Transport failed: > org.apache.activemq.transport.**InactivityIOException: Channel was > inactive for too (>30000) long: /127.0.0.1:54146 | > org.apache.activemq.broker.**TransportConnection.Transport | > InactivityMonitor Async Task: java.util.concurrent.** > ThreadPoolExecutor$Worker@**207a8313 > > I see from Go*gle that this has been a bug in the past. I've tried various > remedies. Nothing works. > > Any help is greatly appreciated. I can't get ActiveMQ to function for more > than a couple minutes because of this. > > Darren > > my connect URI: > tcp://host:port?wireFormat=**openwire&wireFormat.**maxInactivityDuration=0 >
