Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 44607 invoked from network); 15 Nov 2006 14:41:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Nov 2006 14:41:07 -0000 Received: (qmail 76938 invoked by uid 500); 15 Nov 2006 14:41:16 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 76928 invoked by uid 500); 15 Nov 2006 14:41:16 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 76919 invoked by uid 99); 15 Nov 2006 14:41:16 -0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=FORGED_YAHOO_RCVD,FROM_HAS_ULINE_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Nov 2006 06:41:13 -0800 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GkLFt-0007CO-Vn for activemq-users@geronimo.apache.org; Wed, 15 Nov 2006 05:56:45 -0800 Message-ID: <7358006.post@talk.nabble.com> Date: Wed, 15 Nov 2006 05:56:45 -0800 (PST) From: ActiveMQ_User1 To: activemq-users@geronimo.apache.org Subject: VM Transport..please help.. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: web_address1@yahoo.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, We're using Mule and Active MQ (version 3.2.2) in our app - the broker is embedded within Mule and we've specified the brokerUrl as vm://. We're running the app as standalone windows service. However, we've noticed that Active MQ seems to shut down after a while (usually after running for a few days). This is annoying because we have to keep restarting the service every time the broker goes down. I was reading about the vm transport on the website and came across this: The first client to use the VM connection will boot an embedded broker. Subsequent connections will attach that the same broker. Once all VM connections to the broker have been closed, the embedded broker will automatically shutdown. What does that last line imply? Has it got anything to do with my problem? Is there any way to prevent the broker from shutting down or restarting if it did? I read about the failover option..but not sure if that would make a difference. I have also tried using tcp://localhost:61616 instead of vm but that hasn't changed things much either - the broker keeps shutting down. I'm not sure if I have configured things correctly. Here's my Mule Config (just pasting the ActiveMQ part): And here's the broker part of my ActiveMQ config file: Not sure if I need the brokerUrl and a brokerXmlConfig. Any ideas? I'd really appreciate any sort of help - I'm getting a little dejected by it all. Thanks! -- View this message in context: http://www.nabble.com/VM-Transport..please-help..-tf2636226.html#a7358006 Sent from the ActiveMQ - User mailing list archive at Nabble.com.