: If you look at my email the container that is running SOLR got the request : params (http access logs provided in first email) but when it goes through : the SOLR app/code on the container (probably through request filters or : dispatchers..I don't know exactly) its getting lost, which is what I am : trying to understand. I want to understand under what situations this mat : happen.
i can't think of any situation where anything in solr would do this ... i do however note that in the stacktraces you provided from your threaddump, there is a *lot* more forwarding and dispatching going on then i have ever seen in a typical jetty or tomcat type setup -- aprently because of how you have glassfish running you've got the usual stuff prior to the SolrDispatchFilter (org.apache.catalina.*) but you've also got things i have never seen before... com.sun.enterprise.web.WebPipeline com.sun.enterprise.web.PESessionLockingStandardPipeline com.sun.enterprise.web.connector.grizzly.* ...i would bet money that whatever is fausing problems with your request paramaters is happening somewhere in there. It would be trivial to test: just add some logging of the full request params in SolrDispatchFilter and see what it's getting from our servlet container when the doFilter method is called. FWIW, some sporadic googling has lead to a handful of indications that you are not alone in encountering problems with glassfish sporadically swallowing request params (or POST bodies) so that applications running in glassfish don't get them... http://jira.icesoft.org/browse/ICE-5298 http://www.coderanch.com/t/601685/glassfish/Body-Request-occasionally-lost -Hoss
