jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1456) Database connection pooling
Date Thu, 06 Mar 2008 08:48:58 GMT

    [ https://issues.apache.org/jira/browse/JCR-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575617#action_12575617

Jukka Zitting commented on JCR-1456:

> Is it possible to have, in those areas, the same problem reported in JCR-1388?

Connection pools would nicely solve most of our concurrent access issues, as we wouldn't be
constrained to a single connection by default and wouldn't need workarounds like the one in

> The idea is to use a pool package or to build our own?

I'd leverage a pooling DataSource whenever available (JNDI configuration), and use commons-dbcp
to pool explicitly configured connections (JDBC Driver configuration).

> Database connection pooling
> ---------------------------
>                 Key: JCR-1456
>                 URL: https://issues.apache.org/jira/browse/JCR-1456
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>             Fix For: 1.5
> Jackrabbit should use database connection pools instead of a single connection per persistence
manager, cluster journal, or database data store.

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

View raw message