Strange error from [message #470869] |
Tue, 13 November 2007 17:27  |
Eclipse User |
|
|
|
I'm working on a project that involves custom plugins. We are getting
this ClassNotFoundException when we try to launch help in a TrayDialog.
The side tray comes up, but shortly thereafter the exception below pops up.
This does not happen if I open the full Help window and browse/search.
Do we have a missing dependency or something?
java.lang.ExceptionInInitializerError
at
org.apache.lucene.index.IndexWriter.mergeSegments(IndexWrite r.java:674)
at
org.apache.lucene.index.IndexWriter.mergeSegments(IndexWrite r.java:658)
at
org.apache.lucene.index.IndexWriter.optimize(IndexWriter.jav a:517)
at
org.apache.lucene.index.IndexWriter.addIndexes(IndexWriter.j ava:553)
at
org.eclipse.help.internal.search.SearchIndex.merge(SearchInd ex.java:497)
at
org.eclipse.help.internal.search.IndexingOperation.mergeInde xes(IndexingOperation.java:530)
at
org.eclipse.help.internal.search.IndexingOperation.addNewDoc uments(IndexingOperation.java:151)
at
org.eclipse.help.internal.search.IndexingOperation.execute(I ndexingOperation.java:105)
at
org.eclipse.help.internal.search.LocalSearchManager.updateIn dex(LocalSearchManager.java:624)
at
org.eclipse.help.internal.search.LocalSearchManager.ensureIn dexUpdated(LocalSearchManager.java:598)
at
org.eclipse.help.internal.search.federated.IndexerJob.run(In dexerJob.java:27)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.RuntimeException: cannot load SegmentReader class:
java.lang.ClassNotFoundException:
org.apache.lucene.index.CompassSegmentReader
at
org.apache.lucene.index.SegmentReader.<clinit>(SegmentReader.java:97)
... 12 more
|
|
|
|
|
|
Re: Strange error from [message #470928 is a reply to message #470927] |
Thu, 15 November 2007 17:43  |
Eclipse User |
|
|
|
First you should make sure that you have both of the plugins
org.apache.lucene and org.apache.lucene.analysis loaded. Help/About can
show the list of plugins. Second since you have been able to debug this
can you see what happens when and if you hit the line
IndexReader reader = SegmentReader.get(si);
in the case which succeeds, i.e. you open the help window. Does an
exception get thrown which is handled in a way which a user would not
notice.
Also if you open the help window and then do something to cause the tray
dialog to open does the tray dialog work OK in that case or does it
still fail?
Eric Rizzo wrote:
> Chris Goldthorpe wrote:
>> I didn't see this when just using the Eclipse SDK. Are you able to
>> reproduce using an Eclipse SDK or Platform build from the download
>> site? If so you should file a bug report.
>>
>> If this is a bug which is showing up only in your product
>> configuration but not in base Eclipse I'll ask some follow up
>> questions. From the symptoms it's not at all obvious why you are
>> seeing this.
>>
>> What version of Eclipse are you based on?
>
> Eclipse 3.3
>
> This is happening only when we launch a runtime workbench with our
> custom plugins. Must be something in the way our plugins are coded, I
> guess; but I've no idea where to look because the error appears to be
> coming from inside the org.eclipse.help plugin.
> Any help is appreciated.
>
> Eric
|
|
|
Re: Strange error from help indexing service [message #594259 is a reply to message #470869] |
Tue, 13 November 2007 17:39  |
Eclipse User |
|
|
|
Some more analysis done by one of my co-workers:
> The last line of code you can step into before failing is:
> IndexReader reader = SegmentReader.get(si);
>
> Depending on how it is called, SegmentReader tries to load
> either org.apache.lucene.SegmentReader or
> org.apache.lucene.CompassSegmentReader.
> Failure occurs during the load of SegmentReader in this section:
>
> private static final Class IMPL;
> static {
> try {
> String name =
> System.getProperty("org.apache.lucene.SegmentReader.class",
> SegmentReader.class.getName());
> IMPL = Class.forName(name);
> } catch (ClassNotFoundException e) {
> throw new RuntimeException("cannot load SegmentReader class: " + e.toString());
> }
> }
>
> It is not clear why the System property
> "org.apache.lucene.SegmentReader.class" is set when Help is invoked
> from a dialog, but not set when Help is invoked in standalone.
>
> Lame half-workaround:
> Once the indexes have been built (i.e. by performing a search from
> the standalone Help window), they do not need to be rebuilt and this
> failure will not occur even when Help is invoked from within a dialog.
Eric Rizzo wrote:
> I'm working on a project that involves custom plugins. We are getting
> this ClassNotFoundException when we try to launch help in a TrayDialog.
> The side tray comes up, but shortly thereafter the exception below pops up.
> This does not happen if I open the full Help window and browse/search.
> Do we have a missing dependency or something?
>
>
>
> java.lang.ExceptionInInitializerError
> at
> org.apache.lucene.index.IndexWriter.mergeSegments(IndexWrite r.java:674)
> at
> org.apache.lucene.index.IndexWriter.mergeSegments(IndexWrite r.java:658)
> at
> org.apache.lucene.index.IndexWriter.optimize(IndexWriter.jav a:517)
> at
> org.apache.lucene.index.IndexWriter.addIndexes(IndexWriter.j ava:553)
> at
> org.eclipse.help.internal.search.SearchIndex.merge(SearchInd ex.java:497)
> at
> org.eclipse.help.internal.search.IndexingOperation.mergeInde xes(IndexingOperation.java:530)
>
> at
> org.eclipse.help.internal.search.IndexingOperation.addNewDoc uments(IndexingOperation.java:151)
>
> at
> org.eclipse.help.internal.search.IndexingOperation.execute(I ndexingOperation.java:105)
>
> at
> org.eclipse.help.internal.search.LocalSearchManager.updateIn dex(LocalSearchManager.java:624)
>
> at
> org.eclipse.help.internal.search.LocalSearchManager.ensureIn dexUpdated(LocalSearchManager.java:598)
>
> at
> org.eclipse.help.internal.search.federated.IndexerJob.run(In dexerJob.java:27)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
> Caused by: java.lang.RuntimeException: cannot load SegmentReader class:
> java.lang.ClassNotFoundException:
> org.apache.lucene.index.CompassSegmentReader
> at
> org.apache.lucene.index.SegmentReader.<clinit>(SegmentReader.java:97)
> ... 12 more
>
|
|
|
Re: Strange error from [message #594282 is a reply to message #470869] |
Thu, 15 November 2007 12:57  |
Eclipse User |
|
|
|
I didn't see this when just using the Eclipse SDK. Are you able to
reproduce using an Eclipse SDK or Platform build from the download site?
If so you should file a bug report.
If this is a bug which is showing up only in your product configuration
but not in base Eclipse I'll ask some follow up questions. From the
symptoms it's not at all obvious why you are seeing this.
What version of Eclipse are you based on?
|
|
|
Re: Strange error from [message #594292 is a reply to message #470926] |
Thu, 15 November 2007 16:52  |
Eclipse User |
|
|
|
Chris Goldthorpe wrote:
> I didn't see this when just using the Eclipse SDK. Are you able to
> reproduce using an Eclipse SDK or Platform build from the download site?
> If so you should file a bug report.
>
> If this is a bug which is showing up only in your product configuration
> but not in base Eclipse I'll ask some follow up questions. From the
> symptoms it's not at all obvious why you are seeing this.
>
> What version of Eclipse are you based on?
Eclipse 3.3
This is happening only when we launch a runtime workbench with our
custom plugins. Must be something in the way our plugins are coded, I
guess; but I've no idea where to look because the error appears to be
coming from inside the org.eclipse.help plugin.
Any help is appreciated.
Eric
|
|
|
Re: Strange error from [message #594299 is a reply to message #470927] |
Thu, 15 November 2007 17:43  |
Eclipse User |
|
|
|
First you should make sure that you have both of the plugins
org.apache.lucene and org.apache.lucene.analysis loaded. Help/About can
show the list of plugins. Second since you have been able to debug this
can you see what happens when and if you hit the line
IndexReader reader = SegmentReader.get(si);
in the case which succeeds, i.e. you open the help window. Does an
exception get thrown which is handled in a way which a user would not
notice.
Also if you open the help window and then do something to cause the tray
dialog to open does the tray dialog work OK in that case or does it
still fail?
Eric Rizzo wrote:
> Chris Goldthorpe wrote:
>> I didn't see this when just using the Eclipse SDK. Are you able to
>> reproduce using an Eclipse SDK or Platform build from the download
>> site? If so you should file a bug report.
>>
>> If this is a bug which is showing up only in your product
>> configuration but not in base Eclipse I'll ask some follow up
>> questions. From the symptoms it's not at all obvious why you are
>> seeing this.
>>
>> What version of Eclipse are you based on?
>
> Eclipse 3.3
>
> This is happening only when we launch a runtime workbench with our
> custom plugins. Must be something in the way our plugins are coded, I
> guess; but I've no idea where to look because the error appears to be
> coming from inside the org.eclipse.help plugin.
> Any help is appreciated.
>
> Eric
|
|
|
Powered by
FUDForum. Page generated in 0.04926 seconds