[jira] [Commented] (ARTEMIS-2969) broker doesnt handle server-connection being severed

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224707#comment-17224707 ] 

ASF subversion and git services commented on ARTEMIS-2969:
----------------------------------------------------------

Commit c0b12b14c88995a1ca2d3e2c2220aeca220d94b7 in activemq-artemis's branch refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=c0b12b1 ]

ARTEMIS-2969 / ARTEMIS-2937 Controlling connecting state on AMQP Broker Connection

- Fixed an issue where I needed to set connection to null after closing it
- Added more tests on QpidDispatchPeerTest (tests i would have done manually, and reproduced a few issues along the way)


> 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
>             Fix For: 2.16.0
>
>          Time Spent: 0.5h
>  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)