Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 49010 invoked from network); 27 Aug 2007 15:15:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Aug 2007 15:15:44 -0000 Received: (qmail 4771 invoked by uid 500); 27 Aug 2007 15:15:39 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 4623 invoked by uid 500); 27 Aug 2007 15:15:39 -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 4518 invoked by uid 99); 27 Aug 2007 15:15:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2007 08:15:38 -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 (nike.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; Mon, 27 Aug 2007 15:16:25 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1IPgJ7-00045M-61 for users@activemq.apache.org; Mon, 27 Aug 2007 08:15:13 -0700 Message-ID: <12351304.post@talk.nabble.com> Date: Mon, 27 Aug 2007 08:15:13 -0700 (PDT) From: W Bainbridge To: users@activemq.apache.org Subject: JDBC Persistence Problems MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: tysgodhi@travelin.com X-Virus-Checked: Checked by ClamAV on apache.org I'm using ActiveMQ v. 4.1.1 on a Linux machine. When configured for Oracle persistence, it runs fine for awhile--a few hours up to a few days--and then starts getting the checkpoint fails - already started errors (AMQ-1063). The relevant configuration is: Naturally, the stuff in brackets stands for the real values. I've tried both true and false for poolPreparedStatements, and neither setting eliminates the problem. Since we're not live yet I've just disabled jdbc persistence, but I was wondering if the problem exists for all DBMSs, or whether there's a solid, fast DB app I can use for now that will persist OK, until this issue gets fixed. DB persistence is one of the things I used to sell management on ActiveMQ, so it's pretty important for me to get this working as soon as possible. Thanks! W.B. -- View this message in context: http://www.nabble.com/JDBC-Persistence-Problems-tf4336342s2354.html#a12351304 Sent from the ActiveMQ - User mailing list archive at Nabble.com.