Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 74653 invoked from network); 17 Mar 2008 16:54:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Mar 2008 16:54:15 -0000 Received: (qmail 58336 invoked by uid 500); 17 Mar 2008 16:54:10 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 58320 invoked by uid 500); 17 Mar 2008 16:54:10 -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 58297 invoked by uid 99); 17 Mar 2008 16:54:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2008 09:54:10 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of brian.e.munroe@gmail.com designates 64.233.170.187 as permitted sender) Received: from [64.233.170.187] (HELO rn-out-0910.google.com) (64.233.170.187) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2008 16:53:33 +0000 Received: by rn-out-0910.google.com with SMTP id j40so2944408rnf.4 for ; Mon, 17 Mar 2008 09:53:42 -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:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=Ltcj2NlA0Y6Z919baMNPMZ3sgLt2wFjh2KymRAuQkpw=; b=T5vST9h39cTcXye08rR1klcdlFIK57HXf8mRGBbER7y+ZTh30qITM4AifC5jk5hTo/PdHnFQRzS+P+VXse78SB8ht28N+0UHYUvoDEe/z/bFHeFLbdJ8XXvbgStezm4Mgq9etFTuN+p3sYaYO3UAOqyzpuu6WBVpx1JYCuqumyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=cJuu/UcduvkxytYt6Rft8/pR2RNKOoc1l2q0cBstu1xsHuDoiE4Lkl/bXQwiOHHjPxwHvbQhbt5XtTCTxp91yBdYSJxGGuBetn/6XjqJHX0MtbX8hJ4Ci/jtl25M1drFBCofQuguSea3ICLBSxykZtCAVr9GRFaksw0BjbdknwU= Received: by 10.114.156.1 with SMTP id d1mr18256693wae.68.1205772821582; Mon, 17 Mar 2008 09:53:41 -0700 (PDT) Received: by 10.114.108.6 with HTTP; Mon, 17 Mar 2008 09:53:41 -0700 (PDT) Message-ID: <2b39c1040803170953t15f2a115x4bdb0d32c9d32558@mail.gmail.com> Date: Mon, 17 Mar 2008 09:53:41 -0700 From: "Brian Munroe" Reply-To: brian.e.munroe@gmail.com To: "ActiveMQ Users List" Subject: JDBC Database Persistence Question MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org I am trying to determine if JDBC database persistence makes sense in my application stack. Currently I will deploying a single broker (AMQ 5.0) with about 6 queues. What are some of the reasons someone would consider JDBC persistence? Personally, I'm fine with Kaha, but my boss would like me to investigate all the angles. thanks -- brian