You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arthur Naseef (JIRA)" <ji...@apache.org> on 2015/03/06 18:41:38 UTC
[jira] [Resolved] (AMQ-5636) Upgrade the bundled DBCP component.
The current one is very old and buggy.
[ https://issues.apache.org/jira/browse/AMQ-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arthur Naseef resolved AMQ-5636.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.12.0
Assignee: Arthur Naseef
Fixed with commit from Jeff Genender applied with thanks.
> Upgrade the bundled DBCP component. The current one is very old and buggy.
> --------------------------------------------------------------------------
>
> Key: AMQ-5636
> URL: https://issues.apache.org/jira/browse/AMQ-5636
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JDBC, KahaDB
> Affects Versions: 5.10.0, 5.11.0
> Reporter: Paul Gale
> Assignee: Arthur Naseef
> Priority: Critical
> Labels: easyfix
> Fix For: 5.12.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The current DBCP component that ships with ActiveMQ is version 1.4. It dates from Feb 2010.
> After fours years of inactivity a number of releases were made in the last twelve months to the DBCP component. The most recent version, 2.1, was released on Feb 23rd 2015.
> Personally, I am seeing weird behavior with the DBCP 1.4 component when using it as a lease locker with KahaDB. When a connection is dropped the DBCP component doesn't always handle it correctly which manifests itself as a lease lock failure from the broker's standpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)