Yes, export/import will get rid of these corrupt nodes... but as you
said: It's a giant pain. And we too did see not as many corrupted
nodes with newer versions of Magnolia/Jackrabbit.
I have not tested BDB lately though. Checking the WIKI I see that the
BDB setup guide is quite out of date (the last guide is for Mag
3.0.5). Is the setup still the same as with Mag 3.0.5?
-will
On 30.06.2008, at 16:34, SeanMcTex wrote:
The only reliable way we've found to address this sort of JCR
corruption is
to rebootstrap our repository from backup files. It is, of course, a
giant
pain, and takes about 10 hours with the content we've got in there,
so isn't
a very good solution.
On the upside, we've seen much less of this kind of thing with the
most
recent versions of Jackrabbit and the BDB adapter.
Sean
Magnolia - User mailing list wrote:
So what's the standard procedure in these cases. Since they happen
that often, there must be some consent on how to resolve this, right?
Could it be that the MetaData of the nodes which cannot be deleted
are
corrupt in some way... but then this would rather be a Magnolia
problem than a jackrabbit problem.
--
View this message in context:
http://www.nabble.com/The-most-annoying-problem-with-Magnolia-might-be-a-Jackrabbit-problem%3A-Inability-to-delete-nodes-tp18194976p18197047.html
Sent from the Magnolia - User mailing list archive at Nabble.com.
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
