[
https://issues.apache.org/jira/browse/ARTEMIS-2969?focusedWorklogId=506484&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-506484
]
ASF GitHub Bot logged work on ARTEMIS-2969:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Oct/20 01:13
Start Date: 30/Oct/20 01:13
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on a change in pull request
#3322:
URL: https://github.com/apache/activemq-artemis/pull/3322#discussion_r514657893
##########
File path:
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/amqp/connect/AMQPBridgeTest.java
##########
@@ -54,17 +54,6 @@ protected ActiveMQServer createServer() throws Exception {
return createServer(AMQP_PORT, false);
}
- @Test
- public void testsSimpleConnect() throws Exception {
Review comment:
This test was not doing anything at this point..
I had use for it during dev, but as things progressed it is not needed any
longer.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 506484)
Time Spent: 20m (was: 10m)
> broker doesnt handle server-connection being severed
> ----------------------------------------------------
>
> Key: ARTEMIS-2969
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2969
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.16.0
> Reporter: Robbie Gemmell
> Assignee: Clebert Suconic
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The broker doesnt notice or handle a server-connection being severed / timing
> out.
> Start a broker, having instructed it to connect to a router (i.e 'peer'
> configuration). Stop the router (CTRL-C). Start the router again. Broker
> doesnt seem to notice the server-connection is gone and doesnt reconnect. It
> actually sits generating heartbeat frames until its 60sec actual-timeout is
> reached...at which point proton generates a close frame indicating the
> timeout. The broker still doesnt notice the connection is gone, and still
> doesnt reconnect.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
