Hi David,
Seems to me that you might want to try a master slave configuration
instead.. see: http://activemq.com/site/masterslave.html
On 7/26/06, DavidField <[EMAIL PROTECTED]> wrote:
I'm using ActiveMQ 4.0.1 and Mule 1.3-rc4.
I have two instances of ActiveMQ, one on tcp://localhost:61616 and another
on tcp://localhost:61617.
I have set failover on by by the following :
<networkConnectors>
<networkConnector name="default" uri="multicast://default"/>
<networkConnector name="host1 and host2"
uri="static://(tcp://host1:61616,tcp://host2:61617)"
failover="true"/>
</networkConnectors>
In the other ActiveMQ config, I reverse the order of the network
connectors.
In Spring and Mule, the brokerURL: is
"failover:tcp://localhost:61617,tcp://localhost:61616"
What I want to achieve is to have messages received (by Mule) even if one
of
the two instances of ActiveMQ is down. However, I find the following:
* The message will be persisted to the datastore when either ActiveMQ
instance is up - good, as nothing gets lots.
* Messages appear to be sent in turn to one of the two instances, and if a
particular instance is not up then the message will still be persisted but
not sent immediately - bad, I want them all sent straight away.
* Stopping or starting an instance will result in unsent messages being
sent
- bad.
* The same message can be sent multiple times, either when both instances
or
up (rare) or when an instance is either stopped or started (usual) - very
bad.
Any help is mighty appreciated!
--
View this message in context:
http://www.nabble.com/Problems-with-Failover---replication-of-messages-tf2004947.html#a5507084
Sent from the ActiveMQ - User forum at Nabble.com.
--
Regards,
Hiram
Blog: http://hiramchirino.com
