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 > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 13, 2006 9:57 AM > To: [email protected] > Subject: [magnolia-user] MySQL and autoReconnect > > Hi all. > > Unlike the fortunate ones that got magnolia running with > MySQL and autoReconnect=true, I still have problems with this > configuration. I don't know why, but magnolia (jackrabbit?) > simply does not reconnects to MySQL when a connection is > killed, or the server is restarted. > > I made a stupid little program just to test if should work -- > establish a connection, I kill it, stop the server and > restart it later, and the queries issued still work! It > *always* reconnects! > > Anyone has any idea why magnolia does not reconnect at all? > > > Thanks again. > -- > Felipe Braun Azambuja > Departamento de Informática > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
