jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg" <stefan.guggisb...@gmail.com>
Subject Re: Repository inconsistent with xmlpersistentmanager
Date Fri, 19 May 2006 16:37:44 GMT
hi raphaël

On 5/19/06, Raphaël Franchet <raphael@anyware-tech.com> wrote:
> Hello,
> I'm using JR 1.0 with the xmlPersistanceManager.

the XMLPersistenceManager is not recommended to be used
in a production environment. its major flaw , apart from being dead slow ;),
is that it is 'non-transactional', i.e. if your jvm process suffers a
sudden death
(power outage, kill, etc) you'll very likely end up with an
inconsistent repository
state (like the one you described).

by using jackrabbit's default configuration (i.e. DerbyPersistenceManager)
you avoid such issues.


> My application has many nodes (about 20 GB of data) and I've got a huge
> problem : my repository is going inconsistent.
> Using the API normally, I obtain some time the following problem :
> On the file system, node 'A' references a child node 'B' (in his xml
> persistent state) but node 'B' does not exist (there is no corresponding
> xml file).
> The API is telling me that node A has no child, but if I try to add B it
> fails (telling that it can't find the already referenced B).
> The problem appeared once yesterday, so we restored a daily backup (that
> is clean on this node) but after a day of use the same problem is coming
> up (several times on the same repository)
> The only particularity I've noticed on the problematic node, is that it
> is removed and re-added in the same session, quite often.
> The application is used by many people at a time that may be accessing
> the same nodes.
> Any experience or idea ?
> (considering I don't believe this is an astral conjunction)
> Regards,
> --
> Raphaël FRANCHET
> Chef de projet
> Solutions & Technologies
> Tel: +33 (0)5 61 00 73 47
> Fax : +33 (0)5 61 00 51 46
> www.anyware-tech.com

View raw message