So nobody else is having a similar issue that could have some knowledge to
share? The topology I am trying is:
embedded broker -> share nothing master slave -> consumer
I also tried:
embedded broker -> share nothing master slave -> embedded broker -> consumer
and
embedded broker -> shared FS
I'm having a very similar issue. I'm using 5.5 on Linux Ubuntu with Java 6. I
have an embedded broker inside Tomcat forwarding messages to a master slave
share nothing setup. Consumers are in a different machine running Tomcat
connected directly to the master. Everything seems to work just fine whi
Hello Mike,
I think I found a way to make it work:
-no network connector on Master
-on the networked broker a static duplex connector to the Master
-on the Slave a static duplex connector to the networked connector
This way, when the Master is down, the Slave will start its own duplex
connector wi
Hello Garry,
The problem is not with the clients using the failover transport, but on the
remote broker that is using static network connector. For brokers discovery
I cannot use failover but static and this network connector is not behaving
the same way as the failover transport which "connect to
Some steps to help diagnose:
1) enable debug logging for both the client and broker.
org.apache.activemq=DEBUG in the log4j.properties
You should see the client failover transport detect the connection
failure and start retrying
2) A thread dump of the client should also show threads waiting f
Hello Mike,
I have the same problem. I tested and re-tested and it is not working. Have
you found any solution?
I'm currently running it in a Windows environment. The client seems to be
fine, it is the broker that's the issue.
Mike
--
View this message in context:
http://old.nabble.com/Maste
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
To: "users@activemq.apache.org" ; MikeCola
Sent: Mon, March 1, 2010 11:22:47 AM
Subject: Re: Mas
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 c
