activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: "allowLinkStealing" as a client configuration
Date Mon, 18 Sep 2017 14:37:04 GMT
On 09/18/2017 10:25 AM, khandelwalanuj wrote:
> Hi,
>
> I am using ActiveMQv5.14.
>
> We observed issues with durable java subscribers using TCP connector that
> lot of time after client/broker restart clients were not able to connect
> back to the broker and see below exception *"connected from null"*
>
> Lot of time after client restart, we get below exception in logs :
> [2017-09-16 14:15:59.540-0400] [ActiveMQ NIO Worker 3]
> [org.apache.activemq.broker.TransportConnection] [WARN]
> [TransportConnection.java:org.apache.activemq.broker.TransportConnection:processAddConnection()::858]
> [Failed to add Connection
> id=ID:app1a.prod.c.ia55.net-46199-1505585017494-3:2,
> clientId=integratedapp1a.prod.c.ia55.net_conn_listener due to
> javax.jms.InvalidClientIDException: Broker: mqbrokerbaly - Client:
> integratedapp1a.prod.c.ia55.net_conn_listener already *connected from null]
> *
>
> When we check in Jconsole, we don;t find any clients on the topic with the
> same client id.
>
> *To avoid this I wanted to use "allowLinkStealing" configuration in
> ActiveMQ, I found it working when I specify this in broker transport TCP
> configuration. But we don't want to enable it for all, Is there a way we can
> specify this from the client side instead of add in the broker connector
> configuration ?
> *
>
>
No, the broker needs to be configured to do that, client's cannot alter 
the link stealing configuration.


-- 
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message