Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 45859 invoked from network); 25 Oct 2007 13:11:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Oct 2007 13:11:16 -0000 Received: (qmail 977 invoked by uid 500); 25 Oct 2007 13:11:02 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 944 invoked by uid 500); 25 Oct 2007 13:11:02 -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 935 invoked by uid 99); 25 Oct 2007 13:11:02 -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 06:11:02 -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 13:11:05 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Il2TR-00048L-HK for users@activemq.apache.org; Thu, 25 Oct 2007 06:10:09 -0700 Message-ID: <13406436.post@talk.nabble.com> Date: Thu, 25 Oct 2007 06:10:09 -0700 (PDT) From: soloist To: users@activemq.apache.org Subject: Re: Problem using MySql as data source for Persistance Adapter In-Reply-To: <13403660.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: v.soloist@gmail.com References: <13399921.post@talk.nabble.com> <13403331.post@talk.nabble.com> <13403660.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org the only difference is that journaledJDBC is now using built in journal before writing to the db directly.A lot faster but as far as i know not so failsafe in a clustering solution. If you changed that config something like this: this will use directly the db. Which is a lot slower but more reliable if you need a solution like that Mete -- View this message in context: http://www.nabble.com/Problem-using-MySql-as-data-source-for-Persistance-Adapter-tf4688504s2354.html#a13406436 Sent from the ActiveMQ - User mailing list archive at Nabble.com.