[
https://issues.apache.org/jira/browse/ARTEMIS-2327?focusedWorklogId=235769&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235769
]
ASF GitHub Bot logged work on ARTEMIS-2327:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/19 11:54
Start Date: 01/May/19 11:54
Worklog Time Spent: 10m
Work Description: gemmellr commented on issue #2655: ARTEMIS-2327
ExceptionListener invoked when connection level exception
URL: https://github.com/apache/activemq-artemis/pull/2655#issuecomment-488264798
Didnt see most of your edits when replying earlier, but my reply essentially
fits anyway. I havent looked at and am not familiar with the client code
outside the context of this diff. I'm just saying 'always call the exception
listener' for connection exceptions seems out of line with the specs general
desire, except perhaps if those exceptions are always classed as
connection-ending failures, or if the surrounding code such as the failover
stuff is intercepting and handling that, in which case ok.
----------------------------------------------------------------
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: 235769)
Time Spent: 5h (was: 4h 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: 5h
> 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)
