Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 36708 invoked from network); 25 Oct 2007 21:30:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Oct 2007 21:30:41 -0000 Received: (qmail 45110 invoked by uid 500); 25 Oct 2007 21:30:28 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 45088 invoked by uid 500); 25 Oct 2007 21:30:28 -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 45079 invoked by uid 99); 25 Oct 2007 21:30:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2007 14:30: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 (athena.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; Thu, 25 Oct 2007 21:30:31 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IlAHK-0004Pw-Qo for users@activemq.apache.org; Thu, 25 Oct 2007 14:30:10 -0700 Message-ID: <13416441.post@talk.nabble.com> Date: Thu, 25 Oct 2007 14:30:10 -0700 (PDT) From: ttmdev To: users@activemq.apache.org Subject: Re: Is ActiveMQ suitable for this Store-And-Forward scenario? In-Reply-To: <13416012.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: joe.fernandez@ttmsolutions.com References: <13416012.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Yes, ActiveMQ will meet your requirements. You can have the ActiveMQ message broker, on your local client machine, persist the XML messages so that when the network is available it can forward the messages on to the ActiveMQ broker that you have deployed on the server machine. If your client application is somewhat transitory, then you may want to elect not to use an embedded broker and instead deploy a standalone or daemon-like broker on your client machine. Thus you are assured that the persisted messages are forwarded immediately upon the network becoming available. Joe azbel wrote: > > Good afternoon. > I'm currently evaluating existing JMS Servers in order to fulfill the > following requirement: > > A Java client application must send XML messages to JMS on the application > server, but the network is not available most of the time. XML messages > must be persisted in the local client machine and be forwarded when the > connection is available. I suppose that configuring an embedded broker > with ActiveMQ would be the solution since it will persist the messages, > but only if it provides the required funcionality of sending the message > when the network is available again. > > Are my assumptions correct? Does ActiveMQ fulfill the requirement? > Thanks in advance. > > -- View this message in context: http://www.nabble.com/Is-ActiveMQ-suitable-for-this-Store-And-Forward-scenario--tf4693669s2354.html#a13416441 Sent from the ActiveMQ - User mailing list archive at Nabble.com.