[ 
https://issues.apache.org/jira/browse/ARTEMIS-2327?focusedWorklogId=235741&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235741
 ]

ASF GitHub Bot logged work on ARTEMIS-2327:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/May/19 10:50
            Start Date: 01/May/19 10:50
    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-488254772
 
 
   Yes it does. But if its a connection exception it should also make it to the 
connection exception listener. Typically frameworks such as spring rely on 
that. It seems most already do this. This seems to be one corner case it wasn't 
which has been found. So really just plugging that miss.
 
----------------------------------------------------------------
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: 235741)
    Time Spent: 1h 50m  (was: 1h 40m)

> 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: 1h 50m
>  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)

Reply via email to