kmoore4now wrote:
I'm using the journaled JDBC approach to message persistence, with Oracle.
It seems to work well most of the time. However, I'm finding that even
after a normal shutdown a lock occasionally appears to be held on the
activemq_lock table. This prevents ActiveMQ from
Perhaps stating the obvious... this seems to happen when there is some
network instability and the connection to the database is lost. Because the
connection is lost, ActiveMQ is unable to release the lock.
The lock then stays on the table until Oracle is good and ready to delete
it, which can
I think that's a reasonable scenario, Oracle will actually have
trouble detecting them fast enough. I don't know if there's a setting
in Oracle that would speed up the checks. MySQL and MS SQL Server
detect the disconnect almost instantaneous.
However this should not happen on a clean shutdown.
Hi Mario,
Thanks!
The problem does not occur only when ActiveMQ shuts down abnormally. It also
seems to occur when a db connection is lost due to network abnormalities,
while Active MQ is running.
Unfortunately, we do need to run in master / slave mode, so turning off db
locking as you suggest
