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 DE23D177A2 for ; Tue, 31 Mar 2015 00:20:53 +0000 (UTC) Received: (qmail 61132 invoked by uid 500); 31 Mar 2015 00:20:53 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 61066 invoked by uid 500); 31 Mar 2015 00:20:53 -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 61054 invoked by uid 99); 31 Mar 2015 00:20:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2015 00:20:53 +0000 Date: Tue, 31 Mar 2015 00:20:53 +0000 (UTC) From: =?utf-8?Q?Endre_St=C3=B8lsvik_=28JIRA=29?= To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-5694) ActiveMQTempDestination.delete() can block forever MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5694?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Endre St=C3=B8lsvik updated AMQ-5694: -------------------------------- Attachment: thread hangs.png > ActiveMQTempDestination.delete() can block forever > -------------------------------------------------- > > Key: AMQ-5694 > URL: https://issues.apache.org/jira/browse/AMQ-5694 > Project: ActiveMQ > Issue Type: Bug > Reporter: Endre St=C3=B8lsvik > Attachments: thread hangs.png > > > As described in AMQ-5681, we have a setup where we every 10 seconds queri= es the broker over JMS for a StatisticsMessage. > This bug concerns a .. somewhat related .. problem: In that code path, we= delete the temporary reply-to queue after we've read the data. > We've now several times ended up with a peculiar situation where the thre= ad seems to have died. Today I grabbed a JMX console and had a look, and th= e thread is not dead, it is just locked on the delete call. > We have another problem with a shared JDBC "cluster" (the "single master,= hot standbys" setup), where the nodes loose master and effectively goes do= wn. What I believe happens, is that the thread sends the delete message, an= d then goes into a blocking wait for the reply, which never appears, probab= ly because the broker that was master and should have sent it, is now dead. > The delete code path should probably have had some sane timeout, and just= have raised some JMSException - or something. -- This message was sent by Atlassian JIRA (v6.3.4#6332)