Replying to my own post.

I found that 5.11 has a LeaseLockerIOExceptionHandler that seems to be
designed to fix this problem. The use of lease-database-locker on the
persistance adapter and the LeaseLockerIOExceptionHandler on the
brokerService fixed the problem.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Brokerservice-stops-on-DB-failure-tp4695249p4695647.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to