Thanks a lot guys. It was the F5 load balancer. Regards, Sergio
On 28 January 2017 at 01:50, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > That error means that some client talking to your server is attempting to > use an antiquated HTTP protocol version, which was (evidently) supported > by the jetty used in 3.6, but is no longer supported by the jetty used in > 6.2. > > (some details: https://stackoverflow.com/a/32302263/689372 ) > > If it's happening once a second, that sounds like perhaps some sort of > monitoring agent? or perhaps you have a load balancer with an antiquated > health check mechanism? > > > NUANCE NOTE: even though the error specifically mentions "HTTP/0.9" it's > possible that the problematic client is actually attempting to use > HTTP/1.0, but for a vairety of esoteric reasons related to how broadly > formatted HTTP/0.9 requests can be, some HTTP/1.0 requests will look like > "valid" (but unsupported) HTTP/0.9 requests to the jetty server -- hence > that error message... > > https://github.com/eclipse/jetty.project/issues/370 > > > > > : Date: Thu, 26 Jan 2017 08:49:06 -0700 (MST) > : From: marotosg <marot...@gmail.com> > : Reply-To: solr-user@lucene.apache.org > : To: solr-user@lucene.apache.org > : Subject: After migrating to SolrCloud > : > : 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. > : > > -Hoss > http://www.lucidworks.com/ >
