Dave and All, The below exception is not happening anymore when I change the startup port to something else apart from that I had in original startup. The original starup, if I have started without ssl enabled and then startup on the same port with ssl enabled, it is when this warning is happening. But I really need to use the original port that I had. Any suggestion for getting around.
Thanks, Satya java.lang.IllegalArgumentException: No Authority for HttpChannelOverHttp@a01eef8{r=0,c=false,a=IDLE,uri=null} java.lang.IllegalArgumentException: No Authority at org.eclipse.jetty.http.HostPortHttpField.<init>(HostPortHttpField.java:43) On Sun, Feb 26, 2017 at 8:00 PM Dave <hastings.recurs...@gmail.com> wrote: > I don't know about your network setup but a port scanner sometimes can be > an it security device that, well, scans ports looking to see if they're > open. > > > On Feb 26, 2017, at 7:14 PM, Satya Marivada <satya.chaita...@gmail.com> > wrote: > > > > May I ask about the port scanner running? Can you please elaborate? > > Sure, will try to move out to external zookeeper > > > >> On Sun, Feb 26, 2017 at 7:07 PM Dave <hastings.recurs...@gmail.com> > wrote: > >> > >> You shouldn't use the embedded zookeeper with solr, it's just for > >> development not anywhere near worthy of being out in production. > Otherwise > >> it looks like you may have a port scanner running. In any case don't use > >> the zk that comes with solr > >> > >>> On Feb 26, 2017, at 6:52 PM, Satya Marivada <satya.chaita...@gmail.com > > > >> wrote: > >>> > >>> Hi All, > >>> > >>> I have configured solr with SSL and enabled http authentication. It is > >> all > >>> working fine on the solr admin page, indexing and querying process. One > >>> bothering thing is that it is filling up logs every second saying no > >>> authority, I have configured host name, port and authentication > >> parameters > >>> right in all config files. Not sure, where is it coming from. Any > >>> suggestions, please. Really appreciate it. It is with sol-6.3.0 cloud > >> with > >>> embedded zookeeper. Could it be some bug with solr-6.3.0 or am I > missing > >>> some configuration? > >>> > >>> 2017-02-26 23:32:43.660 WARN (qtp606548741-18) [c:plog s:shard1 > >>> r:core_node2 x:plog_shard1_replica1] o.e.j.h.HttpParser parse > exception: > >>> java.lang.IllegalArgumentException: No Authority for > >>> HttpChannelOverHttp@6dac689d{r=0,c=false,a=IDLE,uri=null} > >>> java.lang.IllegalArgumentException: No Authority > >>> at > >>> > >> > org.eclipse.jetty.http.HostPortHttpField.<init>(HostPortHttpField.java:43) > >>> at org.eclipse.jetty.http.HttpParser.parsedHeader(HttpParser.java:877) > >>> at org.eclipse.jetty.http.HttpParser.parseHeaders(HttpParser.java:1050) > >>> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1266) > >>> at > >>> > >> > org.eclipse.jetty.server.HttpConnection.parseRequestBuffer(HttpConnection.java:344) > >>> at > >>> > >> > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:227) > >>> at org.eclipse.jetty.io > >>> .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > >>> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > >>> at > >> > org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:186) > >>> at org.eclipse.jetty.io > >>> .AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) > >>> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > >>> at org.eclipse.jetty.io > >>> .SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) > >>> at > >>> > >> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) > >>> at > >>> > >> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) > >>> at > >>> > >> > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) > >>> at > >>> > >> > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) > >>> at java.lang.Thread.run(Thread.java:745) > >> >