Thanks Shawn, We are using 3.6.2 client and server. I cleared my browser
cache several times while querying (is that similar to clear cache in
solrconfig.xml ?). The query is logged in the solrj based client's
application container however I see it empty in the solr's application
container...so somehow it is getting swallowed by solr...Iam not able to
figure out how and why ?

Thanks
Ravi Kiran Bhaskar

On Fri, Apr 26, 2013 at 4:33 PM, Shawn Heisey <s...@elyograg.org> wrote:

> On 4/26/2013 1:01 PM, Ravi Solr wrote:
> > Hello Shawn,
> >         We found that it is unrelated to the group queries instead more
> > related to the empty queries. Do you happen to know what could cause
> empty
> > queries like the following from SOLRJ ? I can generate similar query via
> > curl hitting the select handler like - http://server:port/solr/select
> >
> >
> server.log_2013-04-26T05-02-22:[#|2013-04-26T04:33:39.065-0400|INFO|sun-appserver2.1.1|org.apache.solr.core.SolrCore|_ThreadID=38;_ThreadName=httpSSLWorkerTh
> > read-9001-11;|[xxxcore] webapp=/solr path=/select params={} hits=24099
> > status=0 QTime=19 |#]
> >
> > What we are seeing is a huge number of these empty queries. Once this
> > happens I have observed 2 things
> >
> > 1. even if I query from admin console, irrespective of the query, I get
> > same results as if its a cached page of *:* query. i.e. I cannot see the
> > query I entered in the server log, the query doesn't even come to the
> > server but I get same results as *:*
> >
> > 2. If I query via solrj no results are returned.
> >
> > This has been driving me nuts for almost a week. Any help is greatly
> > appreciated.
>
> Querying from the admin UI and not seeing anything in the server log
> sounds like browser caching.  You can turn that off in solrconfig.xml.
>
> I could not duplicate what you're seeing with SolrJ.  You didn't say
> what version of SolrJ, so I did this using 3.6.2 (same as your server
> version).  I thought maybe if you had a query object that didn't have an
> actual query set, it might do what you're seeing, but that doesn't
> appear to be the case.  I don't have a 3.6.2 server to test against, so
> I used my 3.5.0 and 4.2.1 servers.
>
> Test code:
> http://pastie.org/private/bnvurz1f9b9viawgqbxvmq
>
> Solr 4.2.1 log:
> INFO  - 2013-04-26 14:17:24.127; org.apache.solr.core.SolrCore; [ncmain]
> webapp=/solr path=/select params={wt=xml&version=2.2} hits=0 status=0
> QTime=20
>
> 3.5.0 server log:
> ----
> Apr 26, 2013 2:20:23 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NullPointerException
>
> Apr 26, 2013 2:20:23 PM org.apache.solr.core.SolrCore execute
> INFO: [ncmain] webapp=/solr path=/select params={wt=xml&version=2.2}
> status=500 QTime=0
> Apr 26, 2013 2:20:23 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NullPointerException
> ----
>
>
> Same code without the setParser line:
>
> Solr 4.2.1 log:
> INFO  - 2013-04-26 14:14:01.270; org.apache.solr.core.SolrCore; [ncmain]
> webapp=/solr path=/select params={wt=javabin&version=2} hits=0 status=0
> QTime=187
>
> Thanks,
> Shawn
>
>

Reply via email to