activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <>
Subject Re: javax.jms.InvalidClientIDException for durable subscription on broker restart
Date Mon, 11 Aug 2014 13:46:51 GMT
On 08/11/2014 06:24 AM, khandelwalanuj wrote:
> Hi,
> I am seeing a weird issue:
> when I restart the ActiveMQ broker a *durable subscriber client* is not able
> to connect to the broker showing "InvalidClientIDException".
> *Exception:
> *Failed to add Connection
> javax.jms.InvalidClientIDException: Broker: mqbrokerprod - Client: GLOCLIENT
> already connected from tcp://
> When I debugged it further I found that only one instance of client is
> trying to connect to the broker, there is no other instance running on
> It looks to me that when broker stopped, at that time broker was not able to
> remove the client ID and somehow it is store in broker. Now when broker
> comes up and client tries to connect to the broker: it gets the
> "InvalidClientIDException" exception.
> Please note that my client is a durable subscriber.
> Ideally broker should remove the client ID at the time of restart. OR should
> I need to do anything else for durable subscribers at the time of
> disconnection ? Please help me here...
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at
The broker doesn't restore previous connections on restart, that's just 
not how it works.  There is most likely another client on that machine 
running or you are using connection pooling and it's attempting to 
create a second connection or some such.

Tim Bish
Sr Software Engineer | RedHat Inc. |
skype: tabish121 | twitter: @tabish121

View raw message