activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-3985) ActiveMQConnection temp advisory consumer should use asyncDispatch - can cause deadlock with slow consumers
Date Tue, 21 Aug 2012 15:00:38 GMT
Gary Tully created AMQ-3985:
-------------------------------

             Summary: ActiveMQConnection temp advisory consumer should use asyncDispatch -
can cause deadlock with slow consumers
                 Key: AMQ-3985
                 URL: https://issues.apache.org/jira/browse/AMQ-3985
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.6.0
            Reporter: Gary Tully
             Fix For: 5.7.0


A slow or blocked connection with the default temp advisory consumer can cause operations
that create advisories to block b/c the dispatch is sync to that advisory consumer. If the
block occurs after the prefetch is filled the broker stores pending messages and the problem
is avoided, but if the block occurs before the prefetch is reached, the dispatch is attempted
in the calling thread, which blocks the originating operation. not good.
The solution is to always request async dispatch for the temp advisory consumer in a client
connection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message