In case an instance goes crazy because of a corrupted index, you can
safely delete the index and restart the application. Luckily
jackrabbit reindexes the content.
Philipp
On 26.01.2007, at 14:46, Claudio Greuter wrote:
Hi Chris, Thanks for your reply
If I remember correctly the Lucene index is used for searching the
repositories. As I am not using this functionality, I a now
thinking of
a way to get rid of it. In case this happens again, would it be enough
to delete the lucene index files or will it mess up the system even
more?
My second question is if it is possible to disable the Lucene index.
Cheers
Claudio
********************************************
IPH Informatik AG
Herr Claudio Greuter
Lagerhausstrasse 9
8400 Winterthur
Switzerland
Tel: +41 (0)52 203 26 72
Fax: +41 (0)52 233 94 71
Email: [EMAIL PROTECTED]
********************************************
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED]
Sent: Freitag, 26. Januar 2007 13:34
To: [email protected]
Subject: Re: [magnolia-user] Tomcat Restart left a corrupted Magnolia
instance
Am Freitag, 26. Januar 2007 12:08 schrieb Claudio Greuter:
What does magnolia write to the webapp folder which could become
corrupt? All data should be saved in the Mysql database (I used
Anthony
Ogiers approach for this).
In a default magnolia configuration the lucene indexing information is
stored
under the webapp directory. Even if you are using mysql, all those
files
under ...webapps/magnolia*/repositories are required. They are the
lucene
index files. This should be configured by the
magnolia.repositories.home
property in the magnolia.properties file.
It is recommended to configure your installation to store this
information
outside of the webapps directory structure.
Here is the exception I mentioned, Any input on this would be great,
because magnolia does not seem to be very stable like this (Tomcat
restarts may be necessary quite often):
Restarting tomcat often shouldn't be a problem when the restart is
achieved
cleanly. The problem isn't so much an issue with Magnolia, but rather
with
the underlying storage mechanism. Specifically, anytime that
jackrabbit
isn't shut down cleanly, there is a risk that its file storage is
inconsistent and no longer usable.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
