Connections are handled by JBoss JCA implementation.
Nuxeo provides a resource adapter for the underlying repository
(jackrabbit) that is registered in JBoss.
Then jboss is using a pool of managed connection and also ensure the
repository resource is enlisted on the current transaction.
In fact if I remember well physical connections to jackrabbit
(jackrabbit sessions) are closed when a managed connection
is reused from the pool. So practically there is a JCR session per
request which is closed after the request ends.
So at nuxeo core level we don't use pooling.
I am not sure if Jackrabbit do some pooling at its level. But I think it
should optimize connections to underlying
databases (or other storages)
Any volunteer to test if pooling on jackrabbit session is improving
perfs.? :)
Bogdan
Cédric Joyau wrote:
Hi,
I'd like to know how Nuxeo handles connections to datasources and the
content repository ... is it a single connection for each one or it is
possible to set up a connection pool ? Do you plan to do some
performance tracking on this ?
Cheers,
Cédric
------------------------------------------------------------------------
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
