Problems with long named parameters with update extract handler

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Problems with long named parameters with update extract handler

Julien Massiera
Hi all,

I recently experienced some problems with the update extract handler on a Solr 7.4.0 instance. When sending a document via multipart POST update request, if a doc parameter name contains too much chars, the POST method fails and I can see the following exception in the Solr logs :

ERROR 2019-06-20T09:43:41,089 (qtp1625082366-13) - Solr|Solr|solr.servlet.HttpSolrCall|[c:FileShare s:shard1 r:core_node2 x:FileShare_shard1_replica_n1] o.a.s.s.HttpSolrCall null:org.apache.commons.fileupload.FileUploadException: Header section has more than 10240 bytes (maybe it is not properly terminated)
                at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362)
                at org.apache.commons.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:115)
                at org.apache.solr.servlet.SolrRequestParsers$MultipartRequestParser.parseParamsAndFillStreams(SolrRequestParsers.java:602)
                at org.apache.solr.servlet.SolrRequestParsers$StandardRequestParser.parseParamsAndFillStreams(SolrRequestParsers.java:784)
                at org.apache.solr.servlet.SolrRequestParsers.parse(SolrRequestParsers.java:167)
                at org.apache.solr.servlet.HttpSolrCall.init(HttpSolrCall.java:317)
                at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:469)
                at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:377)
                at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:323)
                at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1634)
                at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
                at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
                at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
                at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
                at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
                at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
                at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
                at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253)
                at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
                at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
                at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
                at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
                at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155)
                at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
                at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:219)
                at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
                at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
                at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
                at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
                at org.eclipse.jetty.server.Server.handle(Server.java:531)
                at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352)
                at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
                at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281)
                at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102)
                at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
                at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
                at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
                at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
                at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
                at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
                at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:760)
                at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:678)
                at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.commons.fileupload.MultipartStream$MalformedStreamException: Header section has more than 10240 bytes (maybe it is not properly terminated)
                at org.apache.commons.fileupload.MultipartStream.readHeaders(MultipartStream.java:544)
                at org.apache.commons.fileupload.FileUploadBase$FileItemIteratorImpl.findNextItem(FileUploadBase.java:1038)
                at org.apache.commons.fileupload.FileUploadBase$FileItemIteratorImpl.hasNext(FileUploadBase.java:1106)
                at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:339)
                ... 42 more

Under a certain amount of chars in the parameters name, the update request ends up correctly but I am not able to determine the exact amount.
I was not able to find any advices or limitations in the Solr documentation so I am wondering if you consider it as a bug ? otherwise can you tell me what is the exact limitation so I can prevent this error to happen, and can we modify this limitation via configuration ?

Regards,
Julien



---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus