You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Christian Trimble (JIRA)" <ji...@apache.org> on 2010/10/05 00:40:33 UTC

[jira] Updated: (JCR-2767) Database connection leak with DBCP, MySQL, and Observers

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

Christian Trimble updated JCR-2767:
-----------------------------------

    Attachment: connection-helper-thread-safety.patch

This patch makes the ConnectionHelper class thread safe.  This class was not thread safe when running in batch mode, since all threads share the batch mode flag.  This patch replaces that flag with a thread local variable, so every thread accessing the helper can have its own batch connection.

> Database connection leak with DBCP, MySQL, and Observers
> --------------------------------------------------------
>
>                 Key: JCR-2767
>                 URL: https://issues.apache.org/jira/browse/JCR-2767
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.1.0
>         Environment: Jackrabbit with DBCP and MySQL
>            Reporter: Christian Trimble
>         Attachments: connection-helper-thread-safety.patch
>
>
> When using DBCP and MySQL with an observer that modifies the content repository, we are seeing abandoned connections in our connection pool.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.