You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Dave Syer (JIRA)" <ji...@apache.org> on 2009/06/15 16:11:35 UTC

[jira] Created: (AMQ-2289) Browsing Queue through JMX has unintended side effects for producer flow control

Browsing Queue through JMX has unintended side effects for producer flow control
--------------------------------------------------------------------------------

                 Key: AMQ-2289
                 URL: https://issues.apache.org/activemq/browse/AMQ-2289
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMX
    Affects Versions: 5.2.0
            Reporter: Dave Syer


Browsing Queue through JMX has unintended side effects for producer flow control.  If a Producer has blocked because of a MemoryUsage constraint, it will be unblocked (forever) if anyone browses the Queue using JMX (normal use of JMS QueueBrowser does not have the same effect).  This is clearly unintended, since the flow control is bypassed until the broker is restarted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AMQ-2289) Browsing Queue through JMX has unintended side effects for producer flow control

Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/AMQ-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruce Snyder updated AMQ-2289:
------------------------------

    Fix Version/s: 5.5.0
                       (was: 5.4.1)

> Browsing Queue through JMX has unintended side effects for producer flow control
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-2289
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2289
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.2.0
>            Reporter: Dave Syer
>             Fix For: 5.5.0
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Browsing Queue through JMX has unintended side effects for producer flow control.  If a Producer has blocked because of a MemoryUsage constraint, it will be unblocked (forever) if anyone browses the Queue using JMX (normal use of JMS QueueBrowser does not have the same effect).  This is clearly unintended, since the flow control is bypassed until the broker is restarted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.