jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Gash" <Simon.G...@gossinteractive.com>
Subject RE: Repository Fatal Error
Date Mon, 23 May 2005 08:23:17 GMT
I've a feeling its more to do with cfqs storage. Your tool runs fine, it
finds the fault and then repairs the nodes. All very nice but I don't
think its persisting it onces it has repaired the fault. Its almost as
if the session is not being saved ?

Its quite a large repository...so not to sure if you really want me to
zip it up ???



-----Original Message-----
From: Edgar Poce [mailto:edgarpoce@gmail.com] 
Sent: 22 May 2005 17:03
To: jackrabbit-dev@incubator.apache.org
Subject: Re: Repository Fatal Error

Hi Simon

Simon Gash wrote:
> A cool tool with only one draw back, it didn't work :( For some reason
> it found the problem   ok, repaired it and then closed down. It didn't
> actually store the fix, I noticed that the wspStore.dat cqfs file 
> remained untouched. I ran the tool again...same result. Am I missing a

> command line argument ?
There are 3 arguments:
-config="path to repository.xml"
-repository="path to the repository folder"

If you set -repair it will prompt to repair the inconsistency. The class
responsible of fixing the inconsistency generated by the '&' character
is o.a.j.sanitycheck.fix.RemoveChilNodeEntry. If it doesn't work
properly you can plug your custom fix, see the commons chain
configuration file (sanity-check-chain.xml).

If you can't make it work, please send your broken repo in a zip file to
my private address, it might help me to find a bug in the tool.


> Thanks
> Simon
> -----Original Message-----
> From: Edgar Poce [mailto:edgarpoce@gmail.com]
> Sent: 18 May 2005 05:11
> To: jackrabbit-dev@incubator.apache.org
> Subject: Re: Repository Fatal Error
> Hi simon
> Simon Gash wrote:
>>OK I've walked my way through the code and this is what I found.
> ...
>>I guess the solution would be to encode the xml on storage (& = 
>>&amp;), I did this manually and it worked fine. I'm not sure if I 
>>should be checking the new nodes name to ensure its good XML or 
>>whether JackRabbit should be doing it ? Or how about using the CDATA 
>>to block escape literal text ?
> I think you shouldn't do any check, it's a bug in the XML PM.
> One possible fix is to escape the sensitive character ('&'). Or maybe 
> create a DOM document and use XML serialization, I think this would be

> more secure.
> If you still want to recover your broken repository you can try the 
> tool I uploaded to JIRA (http://issues.apache.org/jira/browse/JCR-76).

> It will ask you to remove any reference to nodes and properties that 
> the PM is unable to read. I plan to add a GUI that will let the user 
> navigate the PM, but it's only a console tool for now :(.
> btw, I don't think XML PM + CQFS is a good choice. xml is human 
> readable but it's no so easy to read/write if it's stored in cqfs. 
> IMHO If you need to use cqfs for performance reasons you should use 
> Object PM instead.
> regards
> edgar
>>Any thoughts anyone...
>>Thanks for your time.
> Come visit us at:
> Internet World 2005. June 14 - 16, Earls Court, Stand # A60
> Government Computing Expo. June 21 & 22, Earls Court, Stand # 804
> SOCITM Annual Event. October 16 - 18 Brighton Hotel, Stand # 28 GOSS -

> Ranked 4th in the Deloitte Technology Fast 50 Awards 2004 and 88th in
the Deloitte Technology Fast 500 EMEA.
> This email contains proprietary information, some or all of which may
be legally privileged. It is for the intended recipient only. If an
addressing or transmission error has misdirected this email, please
notify the author by replying to this email. If you are not the intended
recipient you may not use, disclose, distribute, copy, print or rely on
this email. 
> Email transmission cannot be guaranteed to be secure or error free, as
information may be intercepted, corrupted, lost, destroyed, arrive late
or incomplete or contain viruses. This email and any files attached to
it have been checked with virus detection software before transmission.
You should nonetheless carry out your own virus check before opening any
attachment. GOSS Interactive Ltd accepts no liability for any loss or
damage that may be caused by software viruses.

View raw message