Hey guys,
I'm still having trouble with the reliability of connections to our message
bus server when using NMS.  Our ActiveMQ server dies with with OutOfMemory
exceptions about once per week.  At least until 5.2 comes out, I'd like to
automate a nightly restart of the ActiveMQ server, and this leads to my
other problem:

I just can't seem to figure out how to get my .NET services to automatically
reconnect to the message bus when it comes back up.  ActiveMQ server goes
down, clients lose connection, ActiveMQ server comes up, clients never
reconnect until I manually restart them.

I don't know what I'm doing wrong, I've tried setting prefetch values,
transport timeouts, connection timeouts, failover, nothing works.  I have a
trunk build that is about a month old, but I can easily make a new build.

What do I need to do to ensure that our .NET clients will reliably
re-connect to the server when I bounce it?

Thanks,
Bryan

Reply via email to