Hi Hoss,

In a round-about way the changes you asked me to make to the catch block 
led to the solution. It turned out to be an old version of solr in my 
classpath that was being loaded first. I tracked it down after deploying 
your changes and seeing no change to the logging.

A bit foolish of me - it appears to be working fine in Weblogic now. 
Thanks for your help.

Shaun









Chris Hostetter <[EMAIL PROTECTED]>
13/06/2007 19:21
Please respond to solr-user
 
        To:     solr-user@lucene.apache.org
        cc: 
        Subject:        Re: Unfriendly Weblogic




: hmmm... the INFO log suggests it has found my solr.solr.home argument 
ok.

it's more a question of wether or not there were any errors when trying to
load any classes needed to parse your configs (either because they are
staticly refered to, or because they are loaded by reflection based on
your config)

: I don't know how readable the whole stack is but I've included it below.

it's totally readable, but i'm wondering if there are any more log
messages of interest in whatever log you found those in?  possibly earlier
in the file?

: 13-Jun-2007 16:33:16 org.apache.solr.core.SolrConfig initConfig
: INFO: Loaded SolrConfig: solrconfig.xml

this is certainly promising.  It implies (to me anyway) that the
solrconfig.xml is being loaded fine.

: <1181748797062> <BEA-101165> <Could not load user defined filter in
: web.xml: org.apache.solr.servlet.SolrDispatchFilter.
: java.lang.NoClassDefFoundError
:         at
: 
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:75)

this is interesting ... i clearly missread the earlier error mesasage you
had, i thought the problem was SolrDispatchFilter was the subject of the
NoClassDefFoundError, but it's clearly finding SolrDispatchFilter and
having some problem loading another class needed by it (pity weblogic's
classloader doesn't seem to put hte name of hte class it can't find in the
exception)

unless i'm misisng something Line 75 in Solr 1.2 is "SolrCore.log( t )" in
a catch blockfor Throwable, the problem may be that the SolrCore class
can't be loaded at line 69, triggering a NoClassDefFound, which is then
caught and SolrCore is refered to again triggering another NoClassDefFound
which cascades up to weblogic without a more helpful error.


: <1181748797078> <BEA-101216> <Servlet: "SolrServer" failed to preload on
: startup in Web application: "solr.war".
: java.lang.NoClassDefFoundError
:         at org.apache.solr.servlet.SolrServlet.init(SolrServlet.java:48)

this again points to a problem loading SolrCore ... SolrServlet L48 is an
attempt to fetch a SolrCore.

The real question is why can't the SolrCore class be loaded? ... the
static initialization of that class does a lot of stuff, but i would
expect to see more errors about whatever the problem was being logged.

Shaun: if there are no other error messages earlier in yorr logs, and you
are comfortable with java code, would you mid trying to change these lines
in SolrDispatchFilter.init(FilterConfig) ....

    catch( Throwable t ) {
      // catch this so our filter still works
      log.log(Level.SEVERE, "Could not start SOLR. Check solr/home 
property", t);
      SolrConfig.severeErrors.add( t );
      SolrCore.log( t );
    }

to...

    catch( Throwable t ) {
      // catch this so our filter still works
      log.log(Level.SEVERE, "Could not start SOLR. Check solr/home 
property", t);
      SolrConfig.severeErrors.add( t );
      SolrException.logOnce(log,null,e); // TESTING CHANGE IN ERROR 
HANDLING
    }

...and see if that gives you a better error message?


-Hoss


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________




Associated Northcliffe Digital Limited
Registered office: Northcliffe House, 2 Derry Street, London W8 5TT 
Registered in England and Wales with Company no. 03363661

VAT no. GB 243 5711 74 

This e-mail (and any attachments) is confidential and may be privileged. If you 
are not the intended recipient of this message, please notify the sender and do 
not read, copy, use or disclose this communication to others. Any opinions or 
views expressed which are of a personal nature are not necessarily those of the 
company. The company reserves the right to monitor all e-mail communications. 

Reply via email to