Simon Chalmers created ARTEMIS-2172:
---------------------------------------

             Summary: Broker drops connection during throughput test
                 Key: ARTEMIS-2172
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2172
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: AMQP
    Affects Versions: 2.6.3, 2.7.0
         Environment: * Host OS: Linux node1 4.9.0-8-amd64 #1 SMP Debian 
4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux
* Dotnet2.1 SDK installed as per these instructions: 
https://www.microsoft.com/net/download/linux-package-manager/debian9/sdk-current
* Test client attached, to run the test: dotnet AmqpBrokerThroughputTest.dll -h 
<HOST> -u <USER> -p <PASSWORD>, e.g. dotnet AmqpBrokerThroughputTest.dll -h 
172.31.0.175 -u mimqadmin -p dogcat123
* Broker.xml attached.
            Reporter: Simon Chalmers
         Attachments: AmqpBrokerThroughputTest.zip, broker.xml

When running a continual test against a broker setup as a master-slave, after 
an arbitrary length of time, the test client disconnects and stops working. The 
only message thrown in the artemis.log file is:

{{2018-10-31 09:32:07,368 WARN  [org.apache.activemq.artemis.core.client] 
AMQ212037: Connection failure has been detected: AMQ229014: Did not receive 
data from /172.31.15.214:38325 within the 60,000ms connection TTL. The 
connection will now be closed. [code=CONNECTION_TIMEDOUT]
2018-10-31 09:32:07,370 WARN  [org.apache.activemq.artemis.core.server] 
AMQ222061: Client connection failed, clearing up resources for session 
4610a425-dcbf-11e8-b83f-0284a4757140
2018-10-31 09:32:07,371 WARN  [org.apache.activemq.artemis.core.server] 
AMQ222107: Cleared up resources for session 
4610a425-dcbf-11e8-b83f-0284a4757140}}

I wondered if this issue (https://issues.apache.org/jira/browse/ARTEMIS-2146) 
was related, but I tried the test against 2.6.x and the same result happened.  
I've tried it against the current version 2.6.3 and the 2.6.x master in github.

Question: Is there more information available to see why a connection failed?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to