You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@jackrabbit.apache.org by Thomas Fromm <tf...@inubit.com> on 2011/05/18 08:49:11 UTC

Questions to jackrabbit database connection handling

Hi,

these questions are related to jackrabbit 1.6.1:

How works the connection pool? Will be unused sessions closed or is 
there something like an keepalive operation?
How often this (if any) keep-alive will be executed?

thanks in advance,
tf

Re: Questions to jackrabbit database connection handling

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Fri, May 20, 2011 at 10:09 AM, Thomas Fromm <tf...@inubit.com> wrote:
> Yes, after 2.0. But my questions are 1.6 related as mentioned in my original
> post.

There's no database connection pooling in 1.x.

BR,

Jukka Zitting

Re: Questions to jackrabbit database connection handling

Posted by Thomas Fromm <tf...@inubit.com>.

Am 19.05.2011 18:15, schrieb Jukka Zitting:
>> ic. The configured db-connections for the different areas, are they all
>> opened at repository startup and then tried kept open?
>> Or is there a new connection created when nessesary (e.g. a new one created
>> to the data store, when a node is stored and when finished then closed)?
> The implementation uses Commons DBCP for the pooling logic. New
> connections are created when needed, and kept alive for reuse later
> on. See http://wiki.apache.org/jackrabbit/ConnectionPooling for the
> relevant configuration details.

Yes, after 2.0. But my questions are 1.6 related as mentioned in my 
original post.

thanks in advance,
tf

Re: Questions to jackrabbit database connection handling

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Thu, May 19, 2011 at 12:07 PM, Thomas Fromm <tf...@inubit.com> wrote:
> Am 18.05.2011 14:11, schrieb Jukka Zitting:
>> Support for database connection pooling was only added in Jackrabbit
>> 2.0. See https://issues.apache.org/jira/browse/JCR-1456 for the
>> details.
>
> ic. The configured db-connections for the different areas, are they all
> opened at repository startup and then tried kept open?
> Or is there a new connection created when nessesary (e.g. a new one created
> to the data store, when a node is stored and when finished then closed)?

The implementation uses Commons DBCP for the pooling logic. New
connections are created when needed, and kept alive for reuse later
on. See http://wiki.apache.org/jackrabbit/ConnectionPooling for the
relevant configuration details.

BR,

Jukka Zitting

Re: Questions to jackrabbit database connection handling

Posted by Thomas Fromm <tf...@inubit.com>.

Am 18.05.2011 14:11, schrieb Jukka Zitting:
> Support for database connection pooling was only added in Jackrabbit
> 2.0. See https://issues.apache.org/jira/browse/JCR-1456 for the
> details.

ic. The configured db-connections for the different areas, are they all 
opened at repository startup and then tried kept open?
Or is there a new connection created when nessesary (e.g. a new one 
created to the data store, when a node is stored and when finished then 
closed)?

Re: Questions to jackrabbit database connection handling

Posted by Jukka Zitting <ju...@gmail.com>.

Hi,

On Wed, May 18, 2011 at 8:49 AM, Thomas Fromm <tf...@inubit.com> wrote:
> these questions are related to jackrabbit 1.6.1:

Support for database connection pooling was only added in Jackrabbit
2.0. See https://issues.apache.org/jira/browse/JCR-1456 for the
details.

BR,

Jukka Zitting