gration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Wed, Mar 4, 2009 at 5:34 PM, A. Gregory Rabil
> wrote:
>
>>
>> Hi Dejan,
>> No, my application does not terminate. It is still ru
gt; Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Wed, Mar 4, 2009 at 4:53 PM, A. Gregory Rabil
> wrote:
>
>>
>> Hi James,
>> I should clarify my setup:
ection is re-established.
The configuration of my Broker C looks like this:
James.Strachan wrote:
>
> 2009/3/4 A. Gregory Rabil :
>>
>> Hello,
>> I'm using ActiveMQ 5.2.0, and I'm trying to configure a simp
ection is re-established.
The configuration of my Broker C looks like this:
James.Strachan wrote:
>
> 2009/3/4 A. Gregory Rabil :
>>
>> Hello,
>> I'm using ActiveMQ 5.2.0, and I'm trying to configure a simp
Hello,
I'm using ActiveMQ 5.2.0, and I'm trying to configure a simple test of the
"failover" transport. I have two brokers A and B, and a JMS client on a
remote machine. I want the client to connect to Broker A, unless it is
unavailable, in which case it should connect to Broker B. Likewise, if
I am seeing this same problem in AMQ 4.1.1 and 4.1.2. Is there any
resolution to this issue?
Regards,
Greg Rabil
AlB wrote:
>
> I have a network of 3 brokers using 4.0.1 where the maximum hop is 1 (a
> star configuration, a-b-c, where messages travel from a to b or b to c via
> the same queue
