You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2009/07/17 00:16:34 UTC
[jira] Reopened: (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 ]
Bruce Snyder reopened AMQ-1972:
-------------------------------
The changes for this issue caused the {{DefaultDatabaseLocker}} to leak connections. Because the call to close the JDBC connection was removed and a default {{Handler}} implementation (that closes connections) was not provided, the {{DefaultDatabaseLocker.start()}} method now leaks a connection upon every iteration of the while loop. We need to provide a default {{Handler}} impl to at least close the JDBC connection instead of just the simple log statement that's there.
> 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.2.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.