You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by chahir <ch...@yahoo.fr> on 2007/06/04 11:13:53 UTC
ERROR Service
Hi everybody,
I've connected 3 brokers whith static connexions and they were able to
communicate but the problem is that sometimes, one or two brokers face a
problem and display the following error message:
ERROR Service - Async error occurred:
javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
already connected
javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
already connected
How can I resolve this problem please?
I've tried to add a catch block in the transportConnection.java class but
the problem persists.
Thank tou for your advice
--
View this message in context: http://www.nabble.com/ERROR-Service-tf3863922s2354.html#a10946204
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: ERROR Service
Posted by chahir <ch...@yahoo.fr>.
I'm running ActiveMQ 4.2-SNAPSHOT.
Hiram Chirino wrote:
>
> Make sure you are running ActiveMQ 4.1.1 some bugs related to this
> were fixed there.
>
> On 6/4/07, chahir <ch...@yahoo.fr> wrote:
>>
>> Hi everybody,
>> I've connected 3 brokers whith static connexions and they were able to
>> communicate but the problem is that sometimes, one or two brokers face a
>> problem and display the following error message:
>>
>> ERROR Service - Async error occurred:
>> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
>> already connected
>> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
>> already connected
>>
>> How can I resolve this problem please?
>> I've tried to add a catch block in the transportConnection.java class but
>> the problem persists.
>>
>> Thank tou for your advice
>> --
>> View this message in context:
>> http://www.nabble.com/ERROR-Service-tf3863922s2354.html#a10946204
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>
--
View this message in context: http://www.nabble.com/ERROR-Service-tf3863922s2354.html#a11003139
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: ERROR Service
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Make sure you are running ActiveMQ 4.1.1 some bugs related to this
were fixed there.
On 6/4/07, chahir <ch...@yahoo.fr> wrote:
>
> Hi everybody,
> I've connected 3 brokers whith static connexions and they were able to
> communicate but the problem is that sometimes, one or two brokers face a
> problem and display the following error message:
>
> ERROR Service - Async error occurred:
> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
> already connected
> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
> already connected
>
> How can I resolve this problem please?
> I've tried to add a catch block in the transportConnection.java class but
> the problem persists.
>
> Thank tou for your advice
> --
> View this message in context: http://www.nabble.com/ERROR-Service-tf3863922s2354.html#a10946204
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: ERROR Service
Posted by chahir <ch...@yahoo.fr>.
yes Adrian: B1, B2 and B3.
--
View this message in context: http://www.nabble.com/ERROR-Service-tf3863922s2354.html#a10948288
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: ERROR Service
Posted by Adrian Co <ac...@exist.com>.
Does each broker have a unique name?
chahir wrote:
> Hi everybody,
> I've connected 3 brokers whith static connexions and they were able to
> communicate but the problem is that sometimes, one or two brokers face a
> problem and display the following error message:
>
> ERROR Service - Async error occurred:
> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
> already connected
> javax.jms.InvalidClientIDException: Broker: B1 - Client: NC_B2_outbound
> already connected
>
> How can I resolve this problem please?
> I've tried to add a catch block in the transportConnection.java class but
> the problem persists.
>
> Thank tou for your advice
>