It might include situations like when there is a power outage, the client restarts. In this case or any other cases where connection between client and active mq is broken and if the client tries to connect again, it is getting javax.jms.InvalidClientIDException. That is the reason we tried using "allowLinkStealing" on SSL connector.But it is not working. Can you please check if the configuration is correct? Regards, Pavan
Internal Use - Confidential -----Original Message----- From: Jean-Baptiste Onofré <[email protected]> Sent: Tuesday, March 29, 2022 10:38 PM To: [email protected] Subject: Re: "allowLinkStealing" property not working for SSL connector [EXTERNAL EMAIL] Hi, by restart, you mean not a clean client restart right ? It seems your client doesn't disconnect cleanly. Regards JB On Tue, Mar 29, 2022 at 6:11 PM KR, Pavan <[email protected]> wrote: > > Hi, > > > > ActiveMQ version - 5.16.3 > > We are using a client which connects to ActiveMQ over SSL. If the > client restarts, we are getting below exception > > ERROR | Exception in main > javax.jms.InvalidClientIDException: Broker: localhost - Client: > MdmEventsExtractor already connected from tcp://x.x.x.x:53163 > > > > So we tried configuring "allowLinkStealing" for SSL connector, so that when > client restarts and tries to connect with the same client id, it should be > able to connect. > The activemq.xml is attached. With this configuration we are still getting > javax.jms.InvalidClientIDException. > > I can see below log in ActiveMQ startup logs. > INFO | Listening for connections at: > ssl://active-mq-activemq-postgres-666ddbbcd4-fxdsw:61714?allowLinkStea > ling=true&transport.enabledProtocols=TLSv1.2 > > INFO | Connector ssl started > > INFO | Apache ActiveMQ 5.16.3 (master, > ID:active-mq-activemq-postgres-666ddbbcd4-fxdsw-32859-1648553350998-0: > 1) started > > > > Can you please suggest if there anything wrong with the configuration? > > > > Regards, > > Pavan > > > Internal Use - Confidential
activemq.xml
Description: activemq.xml
