You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/02 17:02:04 UTC

[jira] [Commented] (ARTEMIS-1134) Internal errors in AMQP protocol handler can lead to stalled connection

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

ASF GitHub Bot commented on ARTEMIS-1134:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1236


> Internal errors in AMQP protocol handler can lead to stalled connection
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-1134
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1134
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.0.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 2.next
>
>
> In the case where an exception slips through the AMQP event handling code and ends up caught in the event dispatching code the connection has an error condition set on it but is never closed, leaving the remote with no answer to the requested operation and the client must wait for an idle timeout if one is set before the connection is closed.  The broker should remotely close the connection if an uncaught exception gets up into the event dispatcher so that the client is aware that something has gone wrong and requests / connections aren't left hanging.  



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