Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 1605 invoked from network); 18 May 2009 05:13:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 May 2009 05:13:03 -0000 Received: (qmail 17539 invoked by uid 500); 18 May 2009 05:13:02 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 17480 invoked by uid 500); 18 May 2009 05:13:02 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 17470 invoked by uid 99); 18 May 2009 05:13:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 05:13:02 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 05:12:51 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M5v9K-0000vD-BW for users@activemq.apache.org; Sun, 17 May 2009 22:12:30 -0700 Message-ID: <23591185.post@talk.nabble.com> Date: Sun, 17 May 2009 22:12:30 -0700 (PDT) From: lyall To: users@activemq.apache.org Subject: Durable Subscriber and unclean disconnection MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Lyall@The-Pearces.com X-Virus-Checked: Checked by ClamAV on apache.org I am using ActiveMQ 5.2.0 on Windows 2003 Server. Out of the box config. If a client to a topic disconnects, due to failure, or in my case, re-deployment of a BPEL process, it cannot re-connect as ActiveMQ says that it is still connected. I tried 5.3.snapshot (as at 18-May-2009) but that bought a whole slew of new problems, including which interfaces it listens on and trying to establish connections with itself if I attempt to force particular interfaces - at least 5.2.0 works, except for this reconnection point. How can I work around this? Can I? ...Lyall -- View this message in context: http://www.nabble.com/Durable-Subscriber-and-unclean-disconnection-tp23591185p23591185.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.