Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 51580 invoked from network); 30 Jun 2009 11:55:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Jun 2009 11:55:04 -0000 Received: (qmail 75094 invoked by uid 500); 30 Jun 2009 11:55:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 75060 invoked by uid 500); 30 Jun 2009 11:55:14 -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 75050 invoked by uid 99); 30 Jun 2009 11:55:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 11:55:14 +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.155 as permitted sender) Received: from [72.14.220.155] (HELO fg-out-1718.google.com) (72.14.220.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 11:55:04 +0000 Received: by fg-out-1718.google.com with SMTP id e21so24523fga.21 for ; Tue, 30 Jun 2009 04:54:43 -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=5Wd0iSR4E+KakBHjUG9Y1ifdubqkI54duWf0tf0I0pw=; b=h0mbd2Ze3ULmsh276Q8OZR7hIZQNT98y0V2PrabsuqonXg06irHHAv/xEH4OsTLPBG daaHTNWl6m/9nvRhNLEKaWat6aUhclHhUxAy+s4wYjlYdb1gJPMxoaIouCe/R4mniMlb A8AoNoRKfAT4ifpBj6FQWcERwMuYFcpKwanyI= 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=XQf18+iXvS6N8DC9FKMKH4lCVZWUi2FGvJKoJhFuuHtuSKuBdOYvIFA7/BytDDZxMN NMcIDMMyiH6ai0uc4QvpiwFu1mEX9BWuHrfUZK2/TI0ycI5uSa5GNIHflwDwrNcOLn3v EhcjCisT5oO9w/Byn8oGwdMm6yIRyT9ennGh4= MIME-Version: 1.0 Received: by 10.86.74.4 with SMTP id w4mr2597884fga.65.1246362883385; Tue, 30 Jun 2009 04:54:43 -0700 (PDT) In-Reply-To: <24270136.post@talk.nabble.com> References: <24270136.post@talk.nabble.com> Date: Tue, 30 Jun 2009 12:54:42 +0100 Message-ID: <3a73c17c0906300454t6f4e3eb8x84dfbc13d8539864@mail.gmail.com> Subject: Re: Monitoring activemq connection From: Gary Tully To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=000e0cd28e9cece954046d8f784d X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd28e9cece954046d8f784d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit you may want to configure an inactivityTimeout to ensure that a broker network is promptly recognised: see: http://activemq.apache.org/configuring-wire-formats.html 2009/6/30 Tim Sparg > > hi all > > We have an application that receives a lot more messages than it sends. It > sends an appropriate response to every message that it receives, but never > initiates a 'conversation' (for lack of a better term) > > Our problem is that we have very poor lines between the applications that > are running ActiveMQ, so the connection may go down completely, drop > packets > etc etc... > > What then happens is that the application initiating the conversation will > send a message to the appropriate queue, and the receiving app never picks > it up. > > I was looking at the TransportListener class, which looks quite promising > with the onException,transportInterrupted() and transportResumed() methods, > but when i pull out my network cable no error is thrown or methods entered. > My presumption is that these will only be entered/thrown if the application > is sending a message. > > I also tried getting the TransportChannel and then using the isConnected() > method on there, but when i pull my network cable out the method still > returns true. > > I'm currently thinking of making the application attempt a reconnection > after a specified time of inactivity, > thus if the connection is down/not functioning then an exception can be > thrown and the problem managed from there. > However this seems like a fairly shoddy solution, and i'm hoping that > somebody is aware of a better way of checking that the connection is alive. > > thanks > Tim > > -- > View this message in context: > http://www.nabble.com/Monitoring-activemq-connection-tp24270136p24270136.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com --000e0cd28e9cece954046d8f784d--