activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Syer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-2289) Browsing Queue through JMX has unintended side effects for producer flow control
Date Wed, 21 Sep 2011 13:11:09 GMT

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

Dave Syer commented on AMQ-2289:
--------------------------------

JConsole would work, or you could grab the MBean (QueueView) from the server in a unit test.

> 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.x
>
>   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

        

Mime
View raw message