You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2013/04/30 12:04:16 UTC

[jira] [Created] (QPID-4789) Failover at the point FlowControllingBlockingQueue is full can lead to unbound growth (NO_ACK)

Keith Wall created QPID-4789:
--------------------------------

             Summary: Failover at the point FlowControllingBlockingQueue is full can lead to unbound growth (NO_ACK)
                 Key: QPID-4789
                 URL: https://issues.apache.org/jira/browse/QPID-4789
             Project: Qpid
          Issue Type: Bug
          Components: Java Client
    Affects Versions: 0.20, 0.18, 0.16, 0.14, 0.12, 0.10, 0.8, 0.6, 0.22, 0.23
            Reporter: Keith Wall
            Assignee: Keith Wall
            Priority: Minor


If using AMQSession.NO_ACKNOWLEDGE, there is at least one sequence of events that can lead to the FlowControllingBlockingQueue growing without bounds.

For the situation to occur, the FlowControllingBlockingQueue needs to full at the point failover occurs.  After the failover, if new message arrives the FlowControllingBlockingQueue will go beyond its intended limit.   There is nothing preventing FlowControllingBlockingQueue continuing to grow and exhausting all available client memory.

This problem does not affect the standard JMS acknowledgement modes, nor AMQSession.PRE_ACKNOWLEDGE








--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org