If you can't figure it out, you can dynamically change log status for the particular package and/or you could enable access logs to see the request.
Or run Wireshark on the network and see what's going on (when you have a hammer!!!). Regards, Alex. ---- http://www.solr-start.com/ - Resources for Solr users, new and experienced On 26 January 2017 at 10:51, Erick Erickson <erickerick...@gmail.com> wrote: > You probably have an old HTTP jar somewhere in your classpath that's > being found first. Or you have some client somewhere using an old HTTP > version. > > Best, > Erick > > On Thu, Jan 26, 2017 at 7:49 AM, marotosg <marot...@gmail.com> wrote: >> Hi All, >> I have migrated Solr from older versio 3.6 to SolrCloud 6.2 and all good but >> there are almost every second some WARN messages in the logs. >> >> HttpParser >> bad HTTP parsed: 400 HTTP/0.9 not supported for >> HttpChannelOverHttp@16a84451{r=0,​c=false,​a=IDLE,​uri=null} >> >> Anynone knows where are these coming from? >> >> Thanks >> >> >> >> >> -- >> View this message in context: >> http://lucene.472066.n3.nabble.com/After-migrating-to-SolrCloud-tp4315943.html >> Sent from the Solr - User mailing list archive at Nabble.com.
