You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Chris Schmidt (JIRA)" <ji...@apache.org> on 2009/04/15 18:40:15 UTC

[jira] Updated: (JCR-2071) IndexMerger throws null pointer exception without stacktrace

     [ https://issues.apache.org/jira/browse/JCR-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Schmidt updated JCR-2071:
-------------------------------

    Attachment: IndexMerger.patch

Patch to switch the logger to take in the throwable, not just the name of it.

> IndexMerger throws null pointer exception without stacktrace
> ------------------------------------------------------------
>
>                 Key: JCR-2071
>                 URL: https://issues.apache.org/jira/browse/JCR-2071
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>         Environment: Windows OS (XP, Vista)
> Linux RHEL
>  
>            Reporter: Chris Schmidt
>         Attachments: IndexMerger.patch
>
>
> I get the following errors in my log file randomly.  It seems to happen most often when creating the lucene indices, but has happened at other times as well:
> [IndexMerger] ERROR - Error while merging indexes: java.lang.NullPointerException
> The code at org.apache.jackrabbit.core.query.lucene.IndexMerger line 344 appears to be the point where the error is logged, but no other information is provided because the throwable isn't sent to the log (only the toString() version of the exception).  I haven't been able to tell if any indexes are corrupt when this happens.
> I suggest that the logger be changed to determine where the null pointer is coming from first, then resolve the actual issue that is occurring.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.