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. Which version of
ActiveMQ are you using? Maybe there's some problem with the shutdown
in your ActiveMQ-Version.
As a workaround you could turn off the db-locking. But that'll only
work if your not using jdbc-master/slave and if you can make sure that
only one broker is connected. The property to turn off database
locking (not all database locking, but the use of the lock table) is
useDatabaseLock.
So you could f.e. use:
<persistenceAdapter>
<jdbcPersistenceAdapter dataSource="#mysql-ds" useDatabaseLock="false"/>
</persistenceAdapter>
This also works with the journaled jdbc.
Mario
On 10/10/07, kmoore4now <[EMAIL PROTECTED]> wrote:
>
> 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 be a very long time.
>
> As any FYI... it is possible for a DBA to delete the lock manually.
>
> This is very close to a show stopper for us as well.
> --
> View this message in context:
> http://www.nabble.com/lock-on-Oracle-activemq_lock-table-tf4576911s2354.html#a13140350
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
