[
https://issues.apache.org/jira/browse/AMQ-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Robison updated AMQ-3851:
-------------------------------
Attachment: ActiveMqRequestReceiver.cs
ActiveMqMessagingProvider.cs
This is the code I use to wrap the ActiveMQ library that all my other software
uses.
> 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
>
>
> 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
