[
https://issues.apache.org/jira/browse/SOLR-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474302
]
Ryan McKinley commented on SOLR-166:
------------------------------------
I don't see anyway to set load-on-startup for filters. It seems to only work
for servlets. I'm able to fix this problem two ways on resin:
1. remove "<load-on-startup>1</load-on-startup>" from SolrServer servlet
2. lazy load core = SolrCore.getSolrCore()
I think 1 is the better option. Filters are initalized are startup in most
servlet containers. aparently resin first handles the "load-on-startup"
servlets, then moves on to the filters. Jetty does the opposite.
Note, the <load-on-startup>2</load-on-startup> for SolrUpdate does not affect
anything. that servlet just punts anyway.
> trunk requires solr.solr.home set even if JNDI is set
> -----------------------------------------------------
>
> Key: SOLR-166
> URL: https://issues.apache.org/jira/browse/SOLR-166
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Ryan McKinley
>
> The current trunk requires the solr.solr.home property to be set - even if
> JNDI is configured properly.
> I think this is because SolrServlet loads before SolrDispatchFilter and calls
> SolrCore.getSolrCore();
> is there a way to make sure SolrDispatchFilter gets initalized first?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
