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.
On 11/12/06, Vinicius Carvalho <[EMAIL PROTECTED]> wrote:
Hello there. I'm having problems running my examples in a non oracle
database. It seems that activemq uses FOR UPDATE for locking, but with
other databases it throws an error:
<amq:broker useJmx="false" persistent="true" brokerName="localhost">
<amq:persistenceAdapter>
<amq:jdbcPersistenceAdapter id="jdbcAdapter"
dataSource="#dataSource" createTablesOnStartup="true"
></amq:jdbcPersistenceAdapter>
</amq:persistenceAdapter>
<amq:transportConnectors>
<amq:transportConnector
uri="tcp://localhost:61616"></amq:transportConnector>
</amq:transportConnectors>
</amq:broker>
<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<property name="driverClassName">
<value>org.hsqldb.jdbcDriver</value>
</property>
<property name="url">
<value>jdbc:hsqldb:hsql://localhost/testdb</value>
</property>
<property name="username">
<value>sa</value>
</property>
<property name="password">
<value></value>
</property>
</bean>
Any ideas?
Regards
--
IBM Certified SOA Solution Designer
IBM Database Associate - DB2 UDB V8.1 Family
Sun Certified Enterprise Architect (Part I)
--
James
-------
http://radio.weblogs.com/0112098/
