You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2008/10/09 16:29:55 UTC

[jira] Resolved: (AMQ-1972) Pluggable exception handler for JDBC DefaultDatabaseLocker

     [ https://issues.apache.org/activemq/browse/AMQ-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved AMQ-1972.
--------------------------------

    Resolution: Fixed

Implemented in rev 703172

> 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: Hiram Chirino
>             Fix For: 5.3.0
>
>
> 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.