Hi All
Thanks for the replies I tried deleting the folder but the result was
the same. As I do not use the Indexing functionality, I assume I will
deactivate it.
However because I think its an important feature of magnolia, I searched
a bit based on the stacktrace I received and found out the following:
- Lucene is using PDFbox to parse PDF files
- The following part of the exception stacktrace tells me theres a bug
in pdfbox:
Caused by: java.lang.NullPointerException
at org.pdfbox.pdmodel.PDPageNode.getAllKids(PDPageNode.java:194)
The same bug can be found in pdfboxes issue Tracker by searching for
nullpointers, so they know about it but there was no progress since
august of last year :-(
I think (but I am not sure) that magnolia tries to index something on
startup, but fails due to this bug. It seems as if an error during
indexing is the reason that the repository is not loaded.
Does someone with more Magnolia Development Knowledge know if this can
be catched somehow? Because usually its hard to control what stuff
people choose to upload to the CMS, and one corrupt PDF may result in a
corrupted index and a non-working CMS.
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: Donnerstag, 1. Februar 2007 09:17
To: [email protected]
Subject: Re: [magnolia-user] Tomcat Restart left a corrupted Magnolia
instance
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
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
