Hi Philipp
Thanks for the help. Looking forward to see this repair tool also in
CE Magnolia.
-will
On 01.07.2008, at 08:56, Philipp Bracher wrote:
Hi,
Workaround:
- move the corrupt node to a trash section you created
- reimport that node by using create new uuid option
Solution:
- in the progress of latest EE feature development (backup, content
update, ..) we implemented code which can be used to force a
deletion of this nodes on PersistanceManager level (in worst case
you just detach the node from the hierarchy but keep the content in
the db)
- this code will be used to create a kind of repo analyze and repair
tool.
Jackarbbit:
- with magnolia 3.6 you will be able to move from one persistence to
the other (from normal to bundled) by using the new backup feature.
The new bundled PersistanceManager provids a check and repair option
on startup, which might fix several of this issues even when it goes
not as far as it could.
As a EE customer please ask on the support channel for early access
to the tool.
There is a light at the end of the tunnel ;-)
Philipp Bracher
On Jun 30, 2008, at 4:44 PM, Will Scheidegger wrote:
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/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
