From dev-return-31470-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Fri May 18 21:15:31 2012 Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8542ACD44 for ; Fri, 18 May 2012 21:15:30 +0000 (UTC) Received: (qmail 21722 invoked by uid 500); 18 May 2012 21:15:30 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 21683 invoked by uid 500); 18 May 2012 21:15:30 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 21664 invoked by uid 99); 18 May 2012 21:15:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2012 21:15:29 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2012 21:15:28 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id A54B1E168 for ; Fri, 18 May 2012 21:15:08 +0000 (UTC) Date: Fri, 18 May 2012 21:15:08 +0000 (UTC) From: "Chris Robison (JIRA)" To: dev@activemq.apache.org Message-ID: <1209414362.16341.1337375708678.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1841761071.16243.1337374752617.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (AMQ-3851) Infinite TemqQueue advisory messages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AMQ-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Robison updated AMQ-3851: ------------------------------- Attachment: mstmip103-activemq.xml mssd5d101-activemq.xml ActiveMQ server configuration files > 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, 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