Stephen, I realized that it is jackrabbit's problem. I think its distribution is a little strange, you can't find things easily in their site.
Searching through Google, jLibrary (DMS that uses Jackrabbit) has in its documentation an example of using JNDIDatabasePersistenceManager, something that I *hope* would be the best solution, leaving the connection pooling to DBCP. Unfortunately, it seems that it is available only in the development version, along with BerkeleyDBPersistenceManager. Hopefully it'll work. When I get jcr sources, I'll give it a try... It sure would be great if your PersistenceManager was included with jcr ;) Em Sexta 15 Setembro 2006 11:23, Stephen Starkey escreveu: > Hi Felipe, > > Sadly the problem is not with Magnolia, but with Jackrabbit. Jackrabbit's > SimpleDbPersistenceManager uses cached connections and prepared statements. > We had to totally gut and rewrite it (we called it > EnterpriseDbPersistenceManager) to use a Spring-Injected J2EE DataSource. > Now it is much more fault tolerant, and has the advantage of being able to > use DataSource-managed connection- and statement-pooling. > > I was thinking of contributing it back to the JackRabbit folks, but haven't > gotten around to it. Sounds like there's a real need, though, so I'll talk > to my manager about it. > > Stephen Starkey, > Senior Developer, > Backstop Solutions Group. > www.backstopsolutions.com > -- Felipe Braun Azambuja Departamento de Informática ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
