lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <erickerick...@gmail.com>
Subject Re: exception when starting single instance solr-4.0.0
Date Tue, 16 Oct 2012 12:37:25 GMT
Well, it's crude but it _might_ work. All the jars are logged
when loaded on startup. You might search through the
log for "3." or extract all the paths with a regex or something
and see if something jumps out and backtrack.

I really, really, _hate_ having to deal with this kind of thing....

Best
Erick

On Tue, Oct 16, 2012 at 2:12 AM, Bernd Fehling
<bernd.fehling@uni-bielefeld.de> wrote:
> The solr home dir is as suggested for solr 4.0 to be located below jetty.
> So my directory structure is:
> /srv/www/solr/solr-4.0.0/
> -- dist   ** has all apache solr and lucene libs not in .war
> -- lib    ** has all other libs not in .war and not in dist, but required
> -- jetty  ** the jetty copied from solr/example with context, etc, webapps, ...
>    jetty/solr          ** solr with its subdirectories
>    jetty/solr/conf
>    jetty/solr/data
>    jetty/solr/solr.xml
>
> Currently lucene-core is also in lib directory because of the error message.
> I thought this would fix my problem, but no change so if I remove it the error remains.
>
> In solrconfig.xml I have only two lib directives:
> <lib dir="../../dist" />
> <lib dir="../../lib" />
>
>
> Strange thing is, solr/example starts without problems and I could also start
> my solr-4.0.0 development installation from eclipse with runjettyrun.
>
>
> Just tested, after removing lucene-core from lib directory the error remains the same.
>
>
> Seriously a stupid config error, but where?
>
> Regards
> Bernd
>
>
> Am 15.10.2012 21:05, schrieb Chris Hostetter:
>>
>> : SEVERE: null:java.lang.IllegalAccessError:
>> : class org.apache.lucene.codecs.lucene3x.PreFlexRWPostingsFormat cannot access
>> : its superclass org.apache.lucene.codecs.lucene3x.Lucene3xPostingsFormat
>>
>> that sounds like a classpath error.
>>
>> : Very strange, because some lines earlier in the logs I have:
>> :
>> : Oct 15, 2012 2:30:24 PM org.apache.solr.core.SolrConfig initLibs
>> : INFO: Adding specified lib dirs to ClassLoader
>> : Oct 15, 2012 2:30:24 PM org.apache.solr.core.SolrResourceLoader replaceClassLoader
>> : INFO: Adding 'file:/srv/www/solr/solr-4.0.0/lib/lucene-core-4.0-SNAPSHOT.jar' to
classloader
>>
>> ...and that looks like a mistake.  based on that log line, you either have
>> a copy of the lucene core jar in the implicit "lib" dir for your solr
>> core, or you have an explicit <lib ... /> directive pointed
>> somewhere that contains a copy of the lucene-core jar -- either way
>> telling slr to load the lucene-core jar as a plugin.
>>
>> but lucene-core should not be loaded as a plugin.  lucene-core is already
>> in the solr.war, and should have been loaded long before SolrConfig
>> started looking for plugin libraries.
>>
>> which means you probably have two copies of the lucene-core jar ... and
>> if you have two copies of that jar, you probably have two copies of oher
>> lucene jars.
>>
>> which begs the questions:
>>
>>  * what is you solr home dir? (i'me guessing maybe it's
>> "/srv/www/solr/solr-4.0.0/" ?)
>>  * why do you have a copy of lucene-core in /srv/www/solr/solr-4.0.0/lib ?
>>  * what <lib .. /> directives do you have in your solrconfig.xml and why?
>>
>>
>> -Hoss
>>

Mime
View raw message