Hi,
ActiveMQ 5.9.1
I have configured ActiveMQ to use the kaha persistence adapter with a
lease-database-locker.
However, this brings up the question as to which IO exception handler one
should configure: the DefaultIOExceptionHandler or the
JDBCIOExceptionHandler?
The JDBCIOExceptionHandler's method hasLockOwnership() always returns true
if the persistence adapter is not an instance of JDBCPersistenceAdapter
(which it won't be as I'm using kaha). Therefore it cannot be used.
Conversely, the DefaultIOExceptionHandler's hasLockOwnership() method
always returns true, therefore it cannot be used to detect when the
lease-database-locker loses lock ownership.
Is this a bug in the JDBCIOExceptionHandler?
Thanks,
Paul
ActiveMQ 5.9.1
I have configured ActiveMQ to use the kaha persistence adapter with a
lease-database-locker.
However, this brings up the question as to which IO exception handler one
should configure: the DefaultIOExceptionHandler or the
JDBCIOExceptionHandler?
The JDBCIOExceptionHandler's method hasLockOwnership() always returns true
if the persistence adapter is not an instance of JDBCPersistenceAdapter
(which it won't be as I'm using kaha). Therefore it cannot be used.
Conversely, the DefaultIOExceptionHandler's hasLockOwnership() method
always returns true, therefore it cannot be used to detect when the
lease-database-locker loses lock ownership.
Is this a bug in the JDBCIOExceptionHandler?
Thanks,
Paul