From users-return-19107-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon May 18 09:16:01 2009 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 84171 invoked from network); 18 May 2009 09:16:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 May 2009 09:16:01 -0000 Received: (qmail 56784 invoked by uid 500); 18 May 2009 09:16:00 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 56743 invoked by uid 500); 18 May 2009 09:16:00 -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 56733 invoked by uid 99); 18 May 2009 09:16:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 09:16:00 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 72.14.220.152 as permitted sender) Received: from [72.14.220.152] (HELO fg-out-1718.google.com) (72.14.220.152) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 09:15:50 +0000 Received: by fg-out-1718.google.com with SMTP id 16so999472fgg.21 for ; Mon, 18 May 2009 02:15:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=i3ukPx/boFBwMzxqabiaJk3LVt0kfELbli2KXwVa62g=; b=F6yBU6kYyH4fdqkZHMueruZqe//Cys9M5QlkV+6BXGCIBgBFpWsNcG0PbkAoGNNfTC T03RbCbJFxfkfXSqyvFI0Qy0xdfUzFuiJ3FeI6bITI02OissDB1Q9qkqcnaQufAWC1Xx 6ihkvmr519543pnn9SWaEwXs8Jgq0/Q5vHgXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VTR/ADDqgjfRWRTaQ5vrFR0kHH8Pyi+3vfF2IqI+DwXaxWC1o5WvdBdRvzJa5/YcWd MPg2mChVIWh+y1dvSafax1Dr7ZqSAH8eE5LTdId1mR8tJnve0a8KoMiN6E8R8Sjg3LZ1 rt2aMUVtUrTtCIZ3rgwMJW9hdquM/CYkrnZ2g= MIME-Version: 1.0 Received: by 10.86.91.13 with SMTP id o13mr6513798fgb.23.1242638127484; Mon, 18 May 2009 02:15:27 -0700 (PDT) In-Reply-To: <23591185.post@talk.nabble.com> References: <23591185.post@talk.nabble.com> Date: Mon, 18 May 2009 10:15:27 +0100 Message-ID: <3a73c17c0905180215k2b4e4359kfaf2284089fde882@mail.gmail.com> Subject: Re: Durable Subscriber and unclean disconnection From: Gary Tully To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=000e0cd251922c4f19046a2c3c29 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd251922c4f19046a2c3c29 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit seems like a bpel process un/re-deployment logic should be doing an unsubscribe to remove the durable subscription. Failing this, an activemq feature where a configuration option on a durable subscriber could specify an inactivityTimeout after which time an inactive durable subscription would expire could help here. No such feature exists at the moment though. On localhost listens and multiple interfaces with the 5.3-SNAPSHOT, some details can be found in the AMQ-2094 jira issue for that change of behavior. To listen on all interfaces (the old behaviour) you need to specify the wildcard address. Could you comment on that issue with your feedback w.r.t connections to its self so we can get to the bottom of it? thanks. 2009/5/18 lyall > > 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. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com --000e0cd251922c4f19046a2c3c29--