Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 87965 invoked from network); 28 Mar 2008 12:35:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Mar 2008 12:35:30 -0000 Received: (qmail 2679 invoked by uid 500); 28 Mar 2008 12:35:28 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 2654 invoked by uid 500); 28 Mar 2008 12:35:28 -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 2642 invoked by uid 99); 28 Mar 2008 12:35:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Mar 2008 05:35:28 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG 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; Fri, 28 Mar 2008 12:34:38 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JfDnO-0001hj-8o for dev@activemq.apache.org; Fri, 28 Mar 2008 05:34:58 -0700 Message-ID: <16349646.post@talk.nabble.com> Date: Fri, 28 Mar 2008 05:34:58 -0700 (PDT) From: markl16 To: dev@activemq.apache.org Subject: ActiveMQ failover suggesstions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mwilliamson@tssg.org X-Virus-Checked: Checked by ClamAV on apache.org Hi Guys, Just a question about the standard practice with failover. I am currently testing AciveMQ 5 reading and writing TextMessages to numerous queues with no problem as well as using a messageListner. Now at the moment if my activeMQ connection throws an exception as the connection is closed or a message cant be delivered due to the session being closed my application has no way of reconnecting the session. I was just thinking of trying to reconnect to the queue if an exception is thrown from within a catch block or is there a better way of doing this?? Perhaps is there a way to prob a queue to see if it is active without having to write to it or connect to it? best Mark -- View this message in context: http://www.nabble.com/ActiveMQ-failover-suggesstions-tp16349646s2354p16349646.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.