Return-Path: 
 <users-return-9954-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 44746 invoked from network); 19 Jul 2007 12:38:20 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 19 Jul 2007 12:38:20 -0000
Received: (qmail 61964 invoked by uid 500); 19 Jul 2007 12:37:57 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 61927 invoked by uid 500); 19 Jul 2007 12:37:57 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 61918 invoked by uid 99); 19 Jul 2007 12:37:56 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jul 2007 05:37:56 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.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, 19 Jul 2007 05:37:52 -0700
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1IBVG7-0007Yj-C9
	for users@activemq.apache.org; Thu, 19 Jul 2007 05:37:31 -0700
Message-ID: <11688109.post@talk.nabble.com>
Date: Thu, 19 Jul 2007 05:37:31 -0700 (PDT)
From: Dave Syer <david_syer@hotmail.com>
To: users@activemq.apache.org
Subject: Re: Database Locking issues
In-Reply-To: <ec6e67fd0611130727t7ed142dcv1627965d623dc871@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: david_syer@hotmail.com
References: <fde284ef0611120737t51031258u87bd0f1534083c59@mail.gmail.com>
 <ec6e67fd0611130727t7ed142dcv1627965d623dc871@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org


How do you disable the exclusive lock?  Ideally a solution involving Spring
configuration works best for me.  

I am trying to do the same thing as the original post (where the platform
was pretty obviously HSQLDB, by the way).  I guess the HSQLDB support isn't
as complete as it might be?  Or Am I not configuring the adapter correctly?

	<bean class="org.apache.activemq.broker.BrokerService" init-method="start">
		<property name="vmConnectorURI" value="vm://localhost"></property>
		<property name="persistenceAdapter">
			<bean class="org.apache.activemq.store.jdbc.JDBCPersistenceAdapter">
				<property name="dataSource" ref="dataSource"/>
			</bean>
		</property>
	</bean>

	<bean id="connectionFactory"
		class="org.apache.activemq.ActiveMQConnectionFactory">
		<property name="brokerURL">
			<value>vm://localhost</value>
		</property>
	</bean>



James.Strachan wrote:
> 
> So you could disable the exclusive lock we use in ActiveMQ; or if you
> let us know the database you are using and the correct SQL dialect for
> you database we could patch the code to use the correct SQL.
> 

-- 
View this message in context: http://www.nabble.com/Database-Locking-issues-tf2617111s2354.html#a11688109
Sent from the ActiveMQ - User mailing list archive at Nabble.com.