commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DBCP-433) Connection leak when SQLException is thrown while enlisting in XA transaction
Date Mon, 09 Feb 2015 18:47:34 GMT

    [ https://issues.apache.org/jira/browse/DBCP-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312609#comment-14312609
] 

Thomas Neidhart commented on DBCP-433:
--------------------------------------

Ah thats what I missed, the pool has a maximum number of connections it can manage, so if
all connections are leaked the pool can not create more connections.

> Connection leak when SQLException is thrown while enlisting in XA transaction
> -----------------------------------------------------------------------------
>
>                 Key: DBCP-433
>                 URL: https://issues.apache.org/jira/browse/DBCP-433
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: All
>            Reporter: Vladimir Konkov
>         Attachments: DBCP-433_patch.diff, TestManagedConnection.java
>
>
> In ManagedConnection when delegate connection is null new real (driver) connection is
borroved from pool. If SQLExcetion is thrown in 'TransactionContext.enlistResource()'  that
borrowed connection is lost (leaked).
> Short fail on network side may immediately exhaust the pool.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message