Glad you resolved. Thanks for closing the loop. 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 6:12 PM, Darren Govoni <dar...@ontrenet.com> wrote: > Ok, I moved my connection creation into my objects runnable thread and > outside its constructor > and the connections stay up now. Probably something was falling out of > scope or getting gc'd. silly me. > > > On 06/22/2011 11:57 AM, Darren Govoni wrote: > >> Yeah, I can't detect why its happening and the >> >> maxInactivityDuration=0 doesn't work. Maybe I can set a trace to dig >> deeper? >> >> I'm using pyactivemq over activemq-cpp so maybe there are some version >> issues. Not sure. >> >> Maybe the client is busy doing work in its main thread and can't respond >> to the broker >> pings? If that's so, is it common practice to multithread clients? >> >> On 06/22/2011 07:11 AM, Dejan Bosanac wrote: >> >>> 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 >>> >> >> >
