the database-locker uses a long running transaction to maintain exclusive access to a database table. If you are not using maste/slave then you can disable the use of the lock altogether, boolean attribute on the jdbc persistence adapter. The long running transaction has the problem of building up a large transaction log over time. One solution is to use a separate db for the lock table. tha lock data source is separately configurable. in your case it looks like the query is timing out so possibly that config will help if that is your only problem.
A per SuoNayi's succession. the lease locker provides an alternative polling lock that does not require a long running transaction. There is some detail on lockers at: http://activemq.apache.org/pluggable-storage-lockers.html On 10 July 2013 17:48, pkorwar <[email protected]> wrote: > Hi gtully, > > Somebody had posted a solution to this problem which sets the following > configuration for jdbc adapter. > > Is this a good solution to prevent the DB lock issue? What does it actually > do? > > <jdbcPersistenceAdapter ... > > <databaseLocker> > <database-locker queryTimeout="-1" /> > </databaseLocker> > </jdbcPersistenceAdapter> > > Thanks > Pramod > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Activemq-5-8-problem-with-Oracle-jdbc-adapter-tp4669080p4669093.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
