Haven't tried eXo JCR. I think I looked at it about a year ago and the
project seemed to be very static. Has there been any movement there?
As far as Jackrabbit's persistence manager goes, a couple of us have
created our own fixes. The three most basic of the persistence manager
fixes are:
1) Add autoreconnect=true to the end of the mysql connection string.
Mysql connector/j docs don't recommend this, preferring the programmer
check status codes and handling the issue programatically. It's also
been hit or miss as a solution depending on the version of your JDBC
driver. 5.0.3 seems to work (my experience)
2) break up the connection cycle so each method get's a new connection
and closes on exit. Unfortunately this doesn't allow for sql
transactions in the store(ChangeLog) method since store( ChangeLog )
calls other store and delete methods in the same instance.
3) check the sql status on SQLException and reinit the persistence
manager when the status begins with "08" indicating a connection
problem. This the better method and only actually acts when there is a
connection problem. Also have to add logic to each method so operations
are retried when a connection problem occurs.
I have a fix here of which I'm only part way through the testing
(excellent so far). Will post to the list with a jar and additional
info if the remaining tests come back positive.
--David
Felipe Braun Azambuja wrote:
Hi people. It's me. Again :)
Quick question: has anyone tried to use another JSR 170 implementation with
magnolia? I found eXo JCR, looks like it is a good alternative to
Jackrabbit -- don't know if it will solve my MySQL problem, I shall try this
today. If successful, you'll know ;)
Thanks!
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
