lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1419) Solr won't load filters from parent class loader, and the resulting error stacktrace is very confusing
Date Thu, 10 Sep 2009 04:21:57 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753412#action_12753412
] 

Noble Paul commented on SOLR-1419:
----------------------------------

Please ask the question in solr-user/solr-dev before you raise a JIRA issue.

> Solr won't load filters from parent class loader, and the resulting error stacktrace
is very confusing
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1419
>                 URL: https://issues.apache.org/jira/browse/SOLR-1419
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Benson Margulies
>
> I specified a token filter class in my schema, and provided that class in a jar file
in the system classpath of my jetty instance instead of in WEB-INF/lib of my solr webapp.
> This did not work.
> To make matters odder, the logged error did not mention my filter, but rather an internal
solr interface:
> Caused by: java.lang.ClassNotFoundException: org.apache.solr.util.plugin.ResourceLoaderAware
> 	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:319)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
> 	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:399)
> I note in passing that the token filter in turn uses other classes which stayed happily
behind in the outer classloader after moved the immediate filter class into the webapp.

-- 
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