[jira] [Commented] (AMQ-6494) Exceptions and timeouts during shutdown of connectors

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully commented on AMQ-6494:
---------------------------------

There are a few tests in the activemq.all set that fail (65+ runs) with this change. 
I peeked at one, org.apache.activemq.bugs.AMQ2149Test and the failure results in a brokerstopped jms exception bubbling up to the client with the changes. Without the changes the IOException from a disconnect is being handled under the covers by failover: which does a resend.

The fix is to have the app handle that JMS exception which is really a behaviour change. I wonder if there is some middle ground here that will solve the original problem but not change the behaviour and keep those existing failover tests working?
Fixing the test is accepting this new behaviour which may come as a surprise to existing users.

https://builds.apache.org/job/ActiveMQ-Java8-All-UnitTests/org.apache.activemq$activemq-unit-tests/633/testReport/

> Exceptions and timeouts during shutdown of connectors
> -----------------------------------------------------
>
>                 Key: AMQ-6494
>                 URL: https://issues.apache.org/jira/browse/AMQ-6494
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.14.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>             Fix For: 5.15.0
>
>
> During shutdown there are a number of BrokerStoppedException(s) thrown unnecessarily and unnecessary timeouts.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)