[ https://issues.apache.org/jira/browse/AMQ-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467783#comment-13467783 ]
Chris Robison commented on AMQ-3851: ------------------------------------ No, I just made some changes so that the regular cachedLDAPAuthorizationMap would work with Active Directory. Those changes have now been put into trunk so I could still go back to using the regular one and still see the problem. In a previous comment I said that I wrote an extremely simple plugin that always returned the same ACLs and was still able to reproduce the problem. To reproduce the issue, I just setup a simple request/reply system using text messages. I believe I've attached the code I used. There was never a set number of messages I had to send before the flooding started. At first I was only able to reproduce the problem going over VPN, but eventually I was able to reproduce the problem between VMs. > 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 > Assignee: Dejan Bosanac > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira