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 CDB0FDF43 for ; Tue, 17 Jul 2012 12:24:35 +0000 (UTC) Received: (qmail 15638 invoked by uid 500); 17 Jul 2012 12:24:35 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 15558 invoked by uid 500); 17 Jul 2012 12:24:35 -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 15536 invoked by uid 99); 17 Jul 2012 12:24:34 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 12:24:34 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id A5CC3141BF8 for ; Tue, 17 Jul 2012 12:24:34 +0000 (UTC) Date: Tue, 17 Jul 2012 12:24:34 +0000 (UTC) From: "Bhanu (JIRA)" To: dev@activemq.apache.org Message-ID: <1519932254.63510.1342527874680.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhanu updated AMQ-796: ---------------------- Attachment: jstack_amq_5.6.0 > Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive. > ---------------------------------------------------------------------------------------------------------------------- > > Key: AMQ-796 > URL: https://issues.apache.org/jira/browse/AMQ-796 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 4.0, 5.3.0 > Reporter: Hiram Chirino > Assignee: Rob Davies > Fix For: 5.6.0, 4.0.3 > > Attachments: AMQ-796.cmd, jstack_amq_5.6.0 > > > Dejan Reported on the User lists: > Hi, > after some experiments I found that this problem only exists if there are no > other threads in the application. It seems like connection thread dies > before it manages to reconnect. By starting another thread in the > application, it succeeds to recover from master failure and reconnect to the > slave broker. So I have a workaround for now, but it would be nice to make > this work even for simple (single-threaded) clients. > Regards, > Dejan -- 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