I'm currently running it in a Windows environment. The client seems to be fine, it is the broker that's the issue.
Mike ________________________________ From: Josh Carlson <[email protected]> To: "[email protected]" <[email protected]>; MikeCola <[email protected]> Sent: Mon, March 1, 2010 11:22:47 AM Subject: Re: Master/Slave issue with Network of Brokers Is your client hung? Is your client running under Linux? I have a problem where if the actual host machine serving as the master goes down (as opposed to just the process) the client processes hang trying to read/write from the socket connection. I've yet to investigate the issue but was just curious if you were running into the same problem? On 03/01/2010 11:05 AM, MikeCola wrote: > I am running a master/slave broker on 2 servers in a shared-nothing topology > and a networked broker on a third with a duplex connection. When everything > is started up, I am able to produce messages to the master/slave and consume > messages on the networked broker with no problems. However, when I kill the > master , my consumer on the networked broker stops picking up messages from > the queue. Looking at the console messages, it appears that the networked > broker knows the master failed and connects to the slave, but I don’t know > why it won’t consume messages. > http://old.nabble.com/file/p27745457/master-activemq.xml master-activemq.xml > http://old.nabble.com/file/p27745457/slave-activemq.xml slave-activemq.xml > http://old.nabble.com/file/p27745457/remote-activemq.xml remote-activemq.xml >
