JackRabbit doesn't handle pooling at its level, at least not the SimpleDbPersistenceManager. Discussion takes place over here : http://www.mail-archive.com/[EMAIL PROTECTED]/msg04431.html
I'm not an expert, but do you think it's possible to use an existing pooling system and make it work with JackRabbit in Nuxeo ? (reusing the JBoss one for instance, or using the commons-dbcp package from the jakarta project). I'll have a deeper look into this next week.
Any volunteer to test if pooling on jackrabbit session is improving
perfs.? :) Well, I am :) Cedric On 6/8/07, Bogdan Stefanescu <[EMAIL PROTECTED]> wrote:
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
