ArturS created AMQNET-579:
-----------------------------
Summary: ActiveMQ NMS Client hung when connection drops
Key: AMQNET-579
URL: https://issues.apache.org/jira/browse/AMQNET-579
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ, NMS
Affects Versions: 1.7.2
Reporter: ArturS
Attachments: logs.txt
Hello.
We have a cluster which contains 2 brockers (version 5.15.3). Our application
enqueue and dequeue from ActiveMQ in multithread. Each thread create own
connection like this:
{code:java}
var connectionFactory = new ConnectionFactory(connectionString,
settings.ClientId);
return
connectionFactory.CreateConnection(settings.UserName, settings.Password);
{code}
We tests communication between our app and cluster and some scenario is network
connection dropped or brockers vm shutdowns. In this case library can hang (for
dequeue or enqueue).
Connection URI is:
{code:java}
failover:(tcp://dd-amq-app01:61616,tcp://dd-amq-app02:61616)?transport.maxReconnectAttempts=0&transport.startupMaxReconnectAttempts=0&transport.useExponentialBackOff=false&transport.maxReconnectDelay=1000&transport.timeout=10000
{code}
What can we do that library will throw exception or another behavior?
Logs in attach
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
