Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 92124 invoked from network); 19 May 2009 07:03:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 May 2009 07:03:31 -0000 Received: (qmail 51669 invoked by uid 500); 19 May 2009 07:03:31 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 51577 invoked by uid 500); 19 May 2009 07:03:30 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 51567 invoked by uid 99); 19 May 2009 07:03:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 07:03:30 +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 willem.jiang@gmail.com designates 209.85.222.183 as permitted sender) Received: from [209.85.222.183] (HELO mail-pz0-f183.google.com) (209.85.222.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 07:03:20 +0000 Received: by pzk13 with SMTP id 13so2302632pzk.24 for ; Tue, 19 May 2009 00:02:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=DpCHKk97mR9ExUp3wmJngadO3GAkKqgPC5tsz905sK8=; b=Bad4qYrQcytZXqWrZRgeLSlozf/uWDax+AAWCRBX6lNxWKXgg0UZEtyKkt98dzMxZz x1/7KXDw0/rj25tj6HeXNwc51xrwykrpgWk5z3NWK5j+XUSHHNXYQ5ma0P3fdxUUITBV k8CZuKE5c16UvhggSWfV0MpUlFgmISfZRrRVU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=VFQy8JmDgtYwtalUvtrqhAWnD5H25B0F4FgFglNJvUvdhpyr1/8L//0UhiQc9T0Rqo P0G5697FU9OsZBQINpE14GPJpDv1QANB2p9X1Wcd8w7zaSZ1GOXNjoOk44k/0LAHkeT6 p/d2NMidckwCAQZQGYi+ZpbDRnFQykAUOU04U= Received: by 10.142.13.14 with SMTP id 14mr2357632wfm.108.1242716578634; Tue, 19 May 2009 00:02:58 -0700 (PDT) Received: from ?192.168.0.131? ([222.131.243.107]) by mx.google.com with ESMTPS id k2sm10883252rvb.6.2009.05.19.00.02.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 19 May 2009 00:02:58 -0700 (PDT) Message-ID: <4A12599C.709@gmail.com> Date: Tue, 19 May 2009 15:02:52 +0800 From: Willem Jiang User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: JMS transport layer issue. References: <23608046.post@talk.nabble.com> <4A12570B.3060800@die-schneider.net> In-Reply-To: <4A12570B.3060800@die-schneider.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, ActivmeMQ provides a failover transport[1] which could support this feature out of box. You just need to setup right connection URL with it in you JMS endpoint configuration. [1] http://activemq.apache.org/failover-transport-reference.html Willem Christian Schneider wrote: > Hi Hubert, > > normally it will be best to use the reconnect functionality of your jms > system. > For exmple in Tibco JMS you simply give two servers in the jms url or > the same server two times. > Then the jms client will automatically try the two servers alternating. > As soon as at least one server comes > up again your service will work. > > Greetings > > Christian > > Sky-Tiger schrieb: >> Hi all, >> I have a doubt about CXF JMS transport layer. >> Firstly, the JMS server is ok and i had registered a web service >> successfully. But sometime later ,the JMS goes down, my service gets an >> exception, and later the JMS restarts again. >> In such scenario, should i re-register the web serivice again or CXF >> will do it for me automatically? >> >> >> Regards >> >> Hubert. >> > >