Do not do that, I recommend you to use lease lock to instead of the default
long-lived row lock.
At 2013-07-11 00:48:26,pkorwar pkor...@yahoo.com wrote:
Hi gtully,
Somebody had posted a solution to this problem which sets the following
configuration for jdbc adapter.
Is this a good solution
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
Presently I am not using Master/Slave, but we do intend to use it soon. So, I
will try the lease locker and see what happens. Thanks for the response.
Pramod
--
View this message in context:
Thanks for the recommendation !
pramod
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Activemq-5-8-problem-with-Oracle-jdbc-adapter-tp4669080p4669135.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I am using ActiveMQ 5.8 with Oracle as persistent store.
I keep getting the following exception saying that it could not get the DB
lock.
Has anybody faced this issue? Does it have to do with configuration
settings?
I have pasted the exception below.
Thanks
Pramod
2013-07-09
maybe try and reproduce with trace level logging for the broker and
post the results, some more context may help diagnose.
On 10 July 2013 15:15, pkorwar pkor...@yahoo.com wrote:
I am using ActiveMQ 5.8 with Oracle as persistent store.
I keep getting the following exception saying that it
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 /
