Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 3539 invoked from network); 25 Jan 2010 13:25:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2010 13:25:20 -0000 Received: (qmail 26247 invoked by uid 500); 25 Jan 2010 13:25:20 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 26186 invoked by uid 500); 25 Jan 2010 13:25:19 -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 26176 invoked by uid 99); 25 Jan 2010 13:25:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:25:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates 74.125.92.146 as permitted sender) Received: from [74.125.92.146] (HELO qw-out-1920.google.com) (74.125.92.146) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2010 13:25:08 +0000 Received: by qw-out-1920.google.com with SMTP id 5so217842qwc.26 for ; Mon, 25 Jan 2010 05:24:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=stPKBoABtUi9UFSIJS62tYrMQooWkjn0vSoWLOnb9po=; b=ePK43sFi/mpSXQIFqGELNtcqAgjr2kI/oT99n+DbWJTm//wVDJJMm6wtYw5hyJti3M fgrrLmnGcOkdkLfGOGOB/f8YiL4ujgiKkQu4W/o+r7hm5FFaCgIxqIWN2JObkvLPzoLZ 4ZTXQse6LQPG5lm3S1uae6Q/O2ajrgF9i3zw4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=nmRiW30Q30POultU+uqV/aSbbGUVShT3YF2pADA6iZZqoioltNfxpbFPXrwZIMitwp hKEdFj3HZPhf7faHXNZB8deQJ+ISnjMj0i0LP2BXmpAb5KraJl3TM6lYBsg6EXR85zx+ XTnKhaxxxdX7vT7ZJGNHztgi7ylGnLtrsRaf8= Received: by 10.229.14.136 with SMTP id g8mr3796239qca.100.1264425887489; Mon, 25 Jan 2010 05:24:47 -0800 (PST) Received: from ?192.168.2.150? (c-76-21-171-30.hsd1.va.comcast.net [76.21.171.30]) by mx.google.com with ESMTPS id 20sm3061434qyk.9.2010.01.25.05.24.45 (version=SSLv3 cipher=RC4-MD5); Mon, 25 Jan 2010 05:24:46 -0800 (PST) Subject: Re: Subscription lost while From: Timothy Bish To: users@activemq.apache.org In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 25 Jan 2010 08:24:44 -0500 Message-ID: <1264425884.2355.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 (2.28.2-1.fc12) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, 2010-01-25 at 12:18 +0800, Sebastian Rodriguez wrote: > Dear all, > I'm encountering a very strange problem. > I have a client that uses an embedded broker to connect to a network of > brokers. > The connection between my client and the embedded broker is done through the > Apache.NMS.ActiveMQ client. > I'm connecting to the embedded broker through a failover uri as I want to > recover from possible exception raised. > The version of the NMS client is 1.2.0.1794 and we are using the latest > version from 5.3.1 branch. This was also happening with the stable release > 5.3.0. > > Everything works perfectly until I receive the event > ConnectionResumedListener. > The weird part is that: > > - why do I receive a connection resume event without a previous > connection interrupted event? > - the connection is recovered properly, but not my subscription. > Basically my client doesnt receive anything anymore from the embedded broker > although the broker still receives the messages incoming from the network of > brokers. > > Do you have any ideas why I would receive a connection resumed alone > (without a connection interrupted?), and why the failover transport > correctly recovers the connection but not subscriptions? > Thank you very much for your advice on the matter, > Can you enable logging and capture some logs around the time the event is fired? I have not seen any spurious disconnects as yet from NMS. If you have a sample app that can demonstrate the problem that would be helpful. Regards Tim. -- Tim Bish http://fusesource.com http://timbish.blogspot.com/