lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sysdba (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-337) Solr home wrong or missing generates class not found exception
Date Sat, 03 Nov 2007 05:43:14 GMT

    [ https://issues.apache.org/jira/browse/SOLR-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539880
] 

sysdba commented on SOLR-337:
-----------------------------

I have been trying to figure out the missing class problem for days until I came across your
comment that the error message is not valid with respect to the real problem. I wanted to
run Solr within Netbeans 6.0 and nothing I tried worked until I focused on the correct pointer
to the Tomcat 6.0 Catalina/localhost solrconfig.xml file. From reading about Solr with a Google
search, I discovered that it was necessary to add an Environment line in the Catalina/localhost/solr.xml
file to point to solrconfig.xml. Here's the gotcha: the config file containing solrconfig.xml
must reside in a directory with the name "conf", and even more surprising, the pointer in
the solr.xml Environment points to the directory "conf" is in, rather than to "conf" itself.
Apparently Solr automatically expects to find a "conf" directory in the directory being pointed
to. See http://wiki.apache.org/solr/SolrTomcat#head-7036378fa48b79c0797cc8230a8aa0965412fb2e.
Incidentally I changed all the backslashes to forward slashes in file references, althought
this isn't supposed to matter.


> Solr home wrong or missing generates class not found exception
> --------------------------------------------------------------
>
>                 Key: SOLR-337
>                 URL: https://issues.apache.org/jira/browse/SOLR-337
>             Project: Solr
>          Issue Type: Improvement
>         Environment: Tomcat 5.5.23
>            Reporter: Paul Sundling
>            Priority: Minor
>
> If a user types in a bad location for solr/home in  JNDI or doesn't have one set, it
causes a stack trace that has no obvious relationship with the cause (No Class Defined). 
It would be nice if the user got an error message instead about what the problem is.  Given
the number of non-Java users, this could be especially confusing to them. 
> INFO: Solr home set to '/solr_bad_dir/'
> 18:59:38,427 ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/search-solr]
>     Exception starting filter SolrRequestFilter
> java.lang.NoClassDefFoundError
>         at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:74)
>         at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:221)
>         at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:302)
>         at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:78)
>         at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3635)
>         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4222)
>         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760)
>         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740)
>         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
>         at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626)
>         at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
>         at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
>         at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
>         at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
>         at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
>         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022)
>         at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
>         at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
>         at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
>         at org.apache.catalina.core.StandardService.start(StandardService.java:448)
>         at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
>         at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
>         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
> 18:59:38,427 ERROR org.apache.catalina.core.StandardContext
>     Error filterStart
> 18:59:38,427 ERROR org.apache.catalina.core.StandardContext
>     Context [/search-solr] startup failed due to previous errors

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


Mime
View raw message