tp://activemq.apache.org/peer-transport-reference.html
Joe
-Original Message-
From: matt hoffman [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 2:26 PM
To: users@activemq.apache.org
Subject: Re: Help with embedded brokers
Thanks, Joe. Looks like taking out the "duplex=true", w
to:[EMAIL PROTECTED]
> Sent: Thursday, May 01, 2008 1:50 PM
> To: users@activemq.apache.org
> Subject: Re: Help with embedded brokers
>
> Ok, I gave that a shot. I set the broker name to a randomly-generated
> UUID
> (which has implications for durable subscriptions and data reco
You can't have both brokers connect to each other with duplex connections.
Joe
-Original Message-
From: matt hoffman [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 1:50 PM
To: users@activemq.apache.org
Subject: Re: Help with embedded brokers
Ok, I gave that a shot.
What's happening is that you have two brokers with the same name trying to
connect with one another. The exception throws people off because they
always perceive it mean that it has something to do with their client, which
is not always the case. Whenever you see the "NC_" prefix associated with
t
Ok, I gave that a shot. I set the broker name to a randomly-generated UUID
(which has implications for durable subscriptions and data recovery should a
broker go down, I imagine, but it's for the sake of testing). I still got
errors, so I set the network connector name to the same value. It mad
Hi,
you can try specifying different name for every broker. It should help.
Regards
--
Dejan Bosanac
www.scriptinginjava.net
On Thu, May 1, 2008 at 5:29 PM, matt hoffman <[EMAIL PROTECTED]> wrote:
> I'm having a lot of trouble getting embedded brokers to work as they
> should. I'm using them i
