[
https://issues.apache.org/jira/browse/ARTEMIS-2327?focusedWorklogId=235782&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235782
]
ASF GitHub Bot logged work on ARTEMIS-2327:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/19 12:07
Start Date: 01/May/19 12:07
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2655:
ARTEMIS-2327 ExceptionListener invoked when connection level exception
URL: https://github.com/apache/activemq-artemis/pull/2655#issuecomment-488266491
And thats what we're doing. Calling the same connection.fail(e) method that
other blocks and code paths do, within that it does the notification, using the
existing logic thats used for the others paths.
Thus this is why its a nice clean almost one liner fix, because the code and
handling is there in place, just needed to invoke it.
----------------------------------------------------------------
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: 235782)
Time Spent: 7h (was: 6h 50m)
> JMS Connection ExceptionListener not invoked when
> ActiveMQConnectionTimedOutException occurs on sendPacket
> ----------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2327
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2327
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Michael Andre Pearce
> Priority: Major
> Time Spent: 7h
> Remaining Estimate: 0h
>
> When a connection level exception occurs it seems in one case, whilst the
> exception is returned to calling code, exception listeners set at the
> connection are not being invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)