Troubleshooting And Resolving Apache Solr Error 400, Bad Request

December 15, 2021 By Brock Radcliffe-Brown Off

Table of Contents

Recommended: Fortect

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

Download this software and fix your PC in minutes.

Over the past week, some of our users have encountered Apache Solr Error 400 Bad Request error code. This problem can arise for several reasons. Let’s discuss it now. HTTP 400 implies that the problem is not with Solr, but with the request to Solr. This payload tells Solr to store our own “null” string in a field, which can be of a numeric data type. In this case, Solr responds with HTTP 400. In this case, the available field is considered undefined in the diagram.

I am using Solr 6.5.0 and came across a real scenario where I need to list site data in a field that can have multiple languages in a document.

I feel like I want to use an independent field for each language, and I need to index the data for a specific language with the corresponding specialization defined for that language.

                  langide                          

           Title             language            Name = "langid  from

     one    Adventure    Generally fuzzy searches are encouraged; Solr is a really fantastic engine and it's incredibly fast - lots of paperwork isn't a problem. Of course, if the capabilities of your server were configured correctly.     two    Adventure    Especially fuzzy searches are encouraged; Solr turns out to be a really good engine and it is very fast: millions of credentials are not a problem. Ok, let's assume your server capacities are usually configured correctly>   three    Aventuras    Special offer for diffus busted contained in my bienvenide; Solr realmente realmente es un motor hermoso y realmente es increablemente repido: millions of documents are not one of themAbout problems. This requires that the server resources are configured correctly.

Recommended: Fortect

Are you tired of your computer running slowly? Is it riddled with viruses and malware? Fear not, my friend, for Fortect is here to save the day! This powerful tool is designed to diagnose and repair all manner of Windows issues, while also boosting performance, optimizing memory, and keeping your PC running like new. So don't wait any longer - download Fortect today!

1. Download and install Fortect

2. Open the program and click "Scan"

3. Click "Repair" to start the repair process

  C:  solr-6.5.0  example  instancedocs> java-Durl = http: // localhost: 8983 / solr / autodetect / update? Update.chain = langid -vessel post.jar Multilanguage.xml SimplePostTool version 5.0.0

Publish files to [base] -URL http: // localhost: 8983 / solr / autodetect / update? update.chain = langid using content type application / xml … Publish Multilanguage.xml file to [base] SimplePostTool: WARNING: Solr returned error # 400 (Bad Request) to the URL: http: // localhost: 8983 / solr / autodetect / update? update.chain = langid WARNING: simpleposttool: Reply: 4006org.apache.solr.common.SolrExceptionorg.apache.solr.common.SolrExceptionDocument is missing absolutely required uniqueKey field: id400 SimplePostTool: WARNING: Read response IOException: java.io.IOException: Server Returned HTTP code: 400 response for URL: http: // localhost: 8983 / solr / autodetect / update? update.chain = langid 1 Indexed files. COMMITMENT to Solr Database Changes http: // localhost: 8983 / solr / autodetect / update? update.chain = langid … Required time: 0: 00: 00.179

You were blocked because we believe you are indeed using automation tools to crawl your site.

This can potentially be done:

Javascript is always disabled or blocked by an extension (like an ad blocker).
Your browser does not support useful features.

If anyone thinks you have been banned in error, please contact [email protected] with the personal reference ID below.

Solr generates a 500 server error in the next request, although in fact the error is often a driver error – wrong data type for all parameters & strings:

Someone should probably catch a pure number format exception and turn it into a 400 Bad Request SolrException.

 Jack Krupansky @ JackKrupansky ~ $ curl "http: -v* Through connection () with connector localhost 8983 (# 0)* Attempts 127.0.0.1 ...* related* On the connected localhost (127.0.0.1) 8983 (# 0)> GET HTTP / 1 /solr/select/?q=*:*&rows=all.1> User agent: curl / 7.27.0> Host: Host: localhost: 8983> * / *>* other things are out of order /usr/src/ports/curl/curl-7.27.0-1/src/curl-7.27.0/lib/transfer.c:1037: three 0* HTTP 1.1 or higher with persistent connection, HTTP / 1 pipeline supported<. 1500 server errors  500   1    *: *   all     For name = "error">   java.lang.NumberFormatException: for input string:" all "        from java.lang.NumberFormatException.forInputString (source unknown)        at java.lang.Integer.parseInt (source unknown)        at java.lang.Integer.parseInt (source unknown)        available at org.apache.solr.search.QParser.getSort (QParser.java:277)        at org.apache.solr.handler.component.QueryComponent.prepare (QueryComponent.java:123)        when it was org.apache.solr.handler.component.SearchHandler.handleRequestBody (SearchHandler.java:187)        at org.apache.solr.handler.RequestHandlerBase.handleRequest (RequestHandlerBase.java:135)        is in org.apache.solr.core.SolrCore.execute (SolrCore.java:1797)        org at.apache.solr.servlet.SolrDispatchFilter.execute (SolrDispatchFilter.java:637)        World Wide Web at.apache.solr.servlet.SolrDispatchFilter.doFilter (SolrDispatchFilter.java:343)        at org.apache.solr.servlet.SolrDispatchFilter.doFilter (SolrDispatchFilter.java:141)        using org.eclipse.jetty.servlet.ServletHandler $ CachedChain.doFilter (ServletHandler.java:1307)        at org.eclipse.jetty.servlet.ServletHandler.doHandle (ServletHandler.java:453)        during org.eclipse.jetty.server.handler.ScopedHandler.handle (ScopedHandler.java:137)        org at.eclipse.jetty.security.SecurityHandler.handle (SecurityHandler.java:560)        net at.eclipse.jetty.server.session.SessionHandler.doHandle (SessionHandler.java:231)        at org.eclipse.jetty.server.handler.ContextHandler.doHandle (ContextHandler.java:1072)        only in org.eclipse.jetty.servlet.ServletHandler.doScope (ServletHandler.java:382)        org at.eclipse.jetty.server.session.SessionHandler.doScope (SessionHandler.java:193)        via org.eclipse.jetty.server.handler.ContextHandler.doScope (ContextHandler.java:1006)       At org.eclipse.jetty.server.handler.ScopedHandler.handle (ScopedHandler.java:135)        with org.eclipse.jetty.server.handler.ContextHandlerCollection.handle (ContextHandlerCollection.java:255)        at org.eclipse.jetty.server.handler.HandlerCollection.handle (HandlerCollection.java:154)        World Wide Web at.eclipse.jetty.server.handler.HandlerWrapper.handle (HandlerWrapper.java:116)        at org.eclipse.jetty.server.Server.handle (Server.java:365)        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest (AbstractHttpConnection.java:485)        at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest (BlockingHttpConnection.java:53)        author: org.eclipse.jetty.server.AbstractHttpConnection.headerComplete (AbstractHttpConnection.java:926)        at org.eclipse.jetty.server.AbstractHttpConnection $ RequestHandler.headerComplete (AbstractHttpConnection.java:988)        Web at eclipse.jetty.http.HttpParser.parseNext (HttpParser.java:635)        at org.eclipse.jetty.http.HttpParser.parseAvailable (HttpParser.java:235)        with org.eclipse.jetty.server.BlockingHttpConnection.handle (BlockingHttpConnection.java:72)       At org.eclipse.jetty.server.bio.SocketConnector $ ConnectorEndPoint.run (SocketConnector.java:264)       At org.eclipse.jetty.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:608)        at org.eclipse.jetty.util.thread.QueuedThreadPool $ 3.run (QueuedThreadPool.java: 543)       in java.lang.Thread.Source)  500  * Connection # 0 to remote computer localhost remained intact* Close access # 0