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

Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/04/01 13:22:20 UTC

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

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

Gary Tully updated AMQ-2289:
----------------------------

    Fix Version/s:     (was: 5.5.0)
                   5.6.0

> Browsing Queue through JMX has unintended side effects for producer flow control
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-2289
>                 URL: https://issues.apache.org/jira/browse/AMQ-2289
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 5.2.0
>            Reporter: Dave Syer
>             Fix For: 5.6.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira