On Mon, 2011-03-21 at 09:43 -0700, GTsafas wrote: > Hello, > > I currently have an ActiveMQ broker that we use with both Perl (Stomp) and > C++ (Openwire). I am trying to find a solution for timeouts. Here is what I > have tried. > > Perl - Stomp consumers receive heartbeat messages from a seperate producer. > These heartbeat messages are consumed and thrown out. While this have proved > effective I feel like there is a better way to handle this. > > C++ - Currently I am working to find a solution for this. I had thought > adding "keepAlive=true&wireFormat.maxInactivityDuration=0" would do it. But > the other day I got a error due to the channel being inactive for too long.
What version of the C++ client are you using? From where did the inactivity timeouts come, the client or the broker? > > I am replicating what I did in Perl but this is not a proper fix. How do you > all handle this? I am sure it is a common issue. > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Timeouts-tp3394094p3394094.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. Regards -- Tim Bish ------------ FuseSource Email: tim.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
