Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <29173272.post@talk.nabble.com>
Date: Thu, 15 Jul 2010 06:58:11 -0700 (PDT)
From: RJtokenlanring <ing.marco.colombo@gmail.com>
To: users@activemq.apache.org
Subject: Re: Set ClientID - InvalidClientIDException
In-Reply-To: <AANLkTinF7N4JpWQxsVB2_AAWAf7J5XfWFmnbHaMJqgQ6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <29172904.post@talk.nabble.com>
 <AANLkTinF7N4JpWQxsVB2_AAWAf7J5XfWFmnbHaMJqgQ6@mail.gmail.com>


Thank you very much. I'll try failover mecanism.=20
After some tests I see that the code that I have written works correctly
with tcp://
but the above problem only occurs in http:// or in https:// mode.

It could be a bug?


Gary Tully wrote:
>=20
> If you use the failover: protocol, the reconnect will be transparent
> and the broker will be aware of the possibility of a duplicate and
> suppress that exception.
> Otherwise you will need to backoff the reconnect till the broker has a
> chance to recognise and deal with the disconnect
>=20
> On 15 July 2010 14:25, RJtokenlanring <ing.marco.colombo@gmail.com> wrote=
:
>>
>> Hi all,
>> I have a client that do a durable subscriptio to a topic.
>> It register with a static client id.
>>
>> After a connectivity loss (an so a new re-connection), this exception is
>> thrown and connection cannot be
>> re-established:
>>
>> 2010-07-15 13:49:04,700 ERROR - javax.jms.InvalidClientIDException:
>> Broker:
>> localhost - Client: (SchedulerId =3D '1') already connected from
>> blockingQueue_8461294
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroke=
r.java:216)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:=
82)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:=
82)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker=
.java:77)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:=
82)
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0at
>> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:=
82)
>> ....
>>
>> This is not possible, because is the only client with that name and
>> previos
>> connection was closed . .close().
>>
>> There is a way to force reconnection or force that registered client is
>> died
>> and so accept a new connection?
>>
>> I'm using AMQ 5.3.2
>>
>> Thank you and best regards!
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Set-ClientID---InvalidClientIDException-tp29172904=
p29172904.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>=20
>=20
>=20
> --=20
> http://blog.garytully.com
>=20
> Open Source Integration
> http://fusesource.com
>=20
>=20

--=20
View this message in context: http://old.nabble.com/Set-ClientID---InvalidC=
lientIDException-tp29172904p29173272.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.