Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 20 Sep 2011 09:51:08 +0000 (UTC)
From: "Sree Panchajanyam D (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1321931729.45538.1316512268952.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-2289) Browsing Queue through JMX has
 unintended side effects for producer flow control
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sree Panchajanyam D commented on AMQ-2289:
------------------------------------------

Could you tell us how to reproduce this issue? By "browsing the queue using JMX" do u mean using JConsole(internally uses JMX)? 

> 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