Hi Bryan, I would definitely suggest updating to the latest trunk build. I haven't started my reliable testing/verification as I have been tasked with other items. I would think that the new failover protocol support should help in this regard. Prior to that being added, there was no support for automatic reconnect. I haven't played with the failover stuff yet, but I would try listing the same server twice in the failover list so that the code will try to reconnect to the same server if it gets bounced. Don't know if that will work, but it worth a try.
- Jim On Wed, Nov 19, 2008 at 7:55 AM, Bryan Murphy <[EMAIL PROTECTED]> wrote: > 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 >
