Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 31 May 2012 20:32:23 +0000 (UTC)
From: "Chris Robison (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1067039209.23742.1338496343785.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1841761071.16243.1337374752617.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3851) Infinite TemqQueue advisory messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Robison commented on AMQ-3851:
------------------------------------

I've done further testing, I now think the problem is higher up than the DefaultAuthorizationMap in the AuthorizationBroker. I created a very simple class that implements AuthorizationMap that always returns a static set of ACLs and I was able to reproduce the flooding.
                
> Infinite TemqQueue advisory messages
> ------------------------------------
>
>                 Key: AMQ-3851
>                 URL: https://issues.apache.org/jira/browse/AMQ-3851
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Chris Robison
>         Attachments: ActiveMqMessagingProvider.cs, ActiveMqRequestReceiver.cs, Log.zip, mssd5d101-activemq.xml, mstmip103-activemq.xml, run-2012-05-30.snapshot, web-portal-code-snippet.cs
>
>
> I'm seeing a behavior that looks like a race condition of some kind. I have two brokers (MSSD5D101, MSTMIP103). MSSD5D101 has a duplex network connector connecting it to MSTMIP103. The two machines are in different US states so there is a VPN in between. I have two consumer services that reply to queued messages. One consumer (WISD5P101) connects to MSSD5D101 and the other consumer (POSD5P101) connects to MSTMIP103. I also have a web portal that sends messages out to different queues expecting a response. The web portal, and two consumers are all .NET based. 
> What is happening is that after some number of messages, something goes crazy and floods the network of brokers with advisory messages pertaining to temp queues being added or removed. By restarting one or the other of the ActiveMQ servers, things return to normal. But, while the flood is happening, one of the machines will be at 100% CPU and become worthless. I will be attaching logs and some code that I'm using to interact with ActiveMQ.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira