[
https://issues.apache.org/jira/browse/ARTEMIS-2327?focusedWorklogId=235761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235761
]
ASF GitHub Bot logged work on ARTEMIS-2327:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/May/19 11:45
Start Date: 01/May/19 11:45
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-488263475
Something else doing something isnt necessarily a reason to copy it. The
async is in reference to the application not having already been told
synchronously via a method call, which as above the spec doc is clear on.
As I said, it perhaps depends what the exception is, and what reaction is
being taken to it. If this exception always represents the connections ultimate
failure and isnt in response to a particular method call then telling the
exception listener does seem reasonable. If it doesnt, e.g its failing over, or
its only a single methods failure and everythign else is fine, then it often
might not be appropriate.
In particular the async ExceptionListener is good for things only using
MessageListeners, which will never find out otherwise since they dont call
methods [if theres no delivery happening]. Spring uses synchronous receive
calls (by default at least) so it should already discover failures that result
in the connection being considered broken, without the ExceptionListener. If it
doesnt that might point to another issue.
----------------------------------------------------------------
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: 235761)
Time Spent: 4h (was: 3h 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: 4h
> 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)
