"allowLinkStealing" for TCP transport

[khandelwalanuj <kh...@gmail.com>]

Hi, 

I have seen a new feature "allowLinkStealing" with ActiveMQv5.10. This is
supposed to be used with mqtt transport. 

But I have a use case where broker is keeping some stale connection entries
for durable subscribers and not allowing the actually client to connect to
the broker. I discussed it https://issues.apache.org/jira/browse/AMQ-5357
and
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-for-durable-subscription-on-broker-restart-td4684381.html#a4684429 


this options seems to be working for my issue mentioned in above link. I
tested when a normal durable client is connecting to the borker and if other
client tries with the same client id, it still throws exception saying
"javax.jms.JMSException: Durable consumer is in use for client: Test and
subscriptionName: ActiveMQConsumer" 

But when broker keeps stale entries of client ids and actually no client is
connected, then the new client is able to connect properly. 

I just want to know that can I use it for normal tcp transport or will there
be some consequence ? 


Thanks,
Anuj





--
View this message in context: http://activemq.2283324.n4.nabble.com/allowLinkStealing-for-TCP-transport-tp4685860.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: "allowLinkStealing" for TCP transport

[khandelwalanuj <kh...@gmail.com>]

Did Anyone get a chance to look at this ?



--
View this message in context: http://activemq.2283324.n4.nabble.com/allowLinkStealing-for-TCP-transport-tp4685860p4685905.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.