activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: ActiveMQ CPP disconnect While Debugging
Date Wed, 30 Sep 2009 15:20:25 GMT
On Wed, 2009-09-30 at 07:48 -0700, Michael Dehmlow wrote:
> If I debug an activemq-cpp enabled application using visual studio 9.0 it
> appears I get kicked of the broker if I'm broken for more then about 20
> seconds once I resume the application again. This is very annoying as it may
> take a while to get into a particular state and if you spend too long
> steping through code you have to restart all over again. Is there a way to
> get around this problem. 
> 
> My theory is that since all threads in the application are "paused" when a
> break point is hit the active mq thread responsible for handling broker
> traffic is not doing something (keep alive acknowledgment maybe) it is
> supposed to and the broker closes the socket on him.
> 
> Below is the stack trace for the exception generated after being broken too
> long:
> http://www.nabble.com/file/p25682604/exception.gif exception.gif 

Have you tried increasing the max inactivity duration on your client's
connection uri?

param  maxInactivityDuration value = time in milliseconds.

See:  http://activemq.apache.org/configuring-wire-formats.html

Regards
Tim.


Mime
View raw message