Thanks for the quick reply. Looks like that was the secret sauce :-)
ttmdev wrote:
>
> Try taking the 'failover' out of broker A's static connector. Like so,
>
> ... />
>
> With the above static connector, if broker B fails, Broker A should go
> into connect retry mode.
>
>
--
View this
Doh! Never mind my previous question ;)
Joe
ttmdev wrote:
>
> Try taking the 'failover' out of broker A's static connector. Like so,
>
> ... />
>
> With the above static connector, if broker B fails, Broker A should go
> into connect retry mode.
>
> What version of AMQ are you using?
>
>
Try taking the 'failover' out of broker A's static connector. Like so,
With the above static connector, if broker B fails, Broker A should go into
connect retry mode.
What version of AMQ are you using?
Joe
Goto www.ttmsolutions.com for a free ActiveMQ user guide
rmahoney249 wrote:
>
>
On 10 Apr 2008, at 20:14, rmahoney249 wrote:
I'm having a problem with a Network of Brokers in a store and
forward setup.
If I take down the activemq instance on the producer side and then
restart,
it never recreates the DemandForwardingBridge. Here are the details:
Server A (linux, java
I'm having a problem with a Network of Brokers in a store and forward setup.
If I take down the activemq instance on the producer side and then restart,
it never recreates the DemandForwardingBridge. Here are the details:
Server A (linux, java 1.5):
- STOMP Producers putting messages on queue F
