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] Updated: (JCR-1456) Database connection pooling
Date Fri, 15 May 2009 11:16:45 GMT

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

Jukka Zitting updated JCR-1456:
-------------------------------

    Attachment: dbcp.patch

> The problem here is that right now every component (persistence manager, fs,
> journal, ...) in jackrabbit is responsible for creating the database connection
> thus the connection properties are specified as configuration option for the
> component. But connection pooling essentially takes this responsibility from
> component. So how should the database properties be handled? Where
> should the connection pool be configured?

Right where we currently configure the single database connection per component.

> If you have an idea how to configure connection pools and configure the
> components to use those pools while preserving current configuration
> scheme I'd love to know about it.

See the attached patch (dbcp.patch) for a simple change that makes all the connections we
currently create to come from connection pools. This change obviously doesn't solve the main
issue, but should illustrate how I envision us to handle existing database configurations.

> There is one way I can imagine connection pooling working without change
> to configuration syntax. While parsing the configuration jackrabbit would create
> datasource (with default connection pool i.e. dbcp) for each distinct connection
> properties and then pass this datasource to the component to which the
> connection properties belong.

Exactly!


> Database connection pooling
> ---------------------------
>
>                 Key: JCR-1456
>                 URL: https://issues.apache.org/jira/browse/JCR-1456
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>         Attachments: dbcp.patch, patch-1456-1.txt, patch-1456-2.txt, patch-1456-3.txt
>
>
> 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.


Mime
View raw message