[
https://issues.apache.org/activemq/browse/AMQ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Snyder updated AMQ-1972:
------------------------------
Attachment: AMQ-1972.patch.txt
Actually, after looking closer, the problem is not the lack of a default
{{Hander}} impl. The problem is due to the fact that the finally clause where
the connection is closed was removed. I've added a try/finally clause back in
specifically to close the connection. See the attached patch.
> Pluggable exception handler for JDBC DefaultDatabaseLocker
> ----------------------------------------------------------
>
> Key: AMQ-1972
> URL: https://issues.apache.org/activemq/browse/AMQ-1972
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Hiram Chirino
> Assignee: Bruce Snyder
> Fix For: 5.3.0
>
> Attachments: AMQ-1972.patch.txt
>
>
> Sometimes folks want to use a custom error handler when using a custom
> database locking strategy.. that way they can inspect the error message for
> known SQL error codes and such.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
