Found the issue. This was old code that I finally got around to enabling.
Somebody put a slash at the end of my XML element.
________________________________
From: Yonik Seeley <ysee...@gmail.com>
To: solr-user@lucene.apache.org
Sent: Thursday, April 2, 2009 2:32:37 PM
Subject: Re: newSearcher doesn't fire
I just tried with the standard example in solr trunk... seems like
it's still working fine when I issue a commit:
Apr 2, 2009 5:30:19 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener sending requests to searc...@1702c48 main
Apr 2, 2009 5:30:19 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=null path=null params={rows=10&start=0&q=solr} hits=2 status=0 Q
Time=1
Apr 2, 2009 5:30:19 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=null path=null params={rows=10&start=0&q=rocks} hits=0 status=0
QTime=1
Apr 2, 2009 5:30:19 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=null path=null params={q=static+newSearcher+warming+query+from+s
olrconfig.xml} hits=0 status=0 QTime=1
Apr 2, 2009 5:30:19 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener done.
-Yonik
http://www.lucidimagination.com
On Thu, Apr 2, 2009 at 5:25 PM, Kevin Osborn <osbo...@yahoo.com> wrote:
> I am trying to figure this out. I have a firstSearcher and a newSearcher
> event. They are almost identical. Upon startup, I see all the firstSearcher
> events in my log. I also see log events for Added SolrEventListener for both
> firstSearcher and newSearcher.
>
> Next, I push out a new index. I see that my caches get regenerated and the
> new searcher is registered. However, I don't see my newSearcher events get
> fired. This is verifed in the Solr cache hits as well. And the logs show no
> errors or even any messages at all regarding newSearcher.
