My SolrJ client uses ConcurrentUpdateSolrServer to index > 50Gs of docs to a
SOLR 3.6 instance on my Linux box.  When running the same client against
SOLR 4.2.1 on EC2 I got the following:


SolrJ client error
====================================================================
request: http://ec2-103-x-x-x.compute-3.amazonaws.com/solr/mycore/update
        at
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner.run(ConcurrentUpdateSolrServer.java:189)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
12593 [pool-1-thread-2] INFO
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer - finished:
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer$Runner@7eb1cc87
12593 [pool-1-thread-5] INFO
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer - Status for:
doc-123b166-a2fd-11e0-94b3-842b2b170032 is 400
12593 [pool-1-thread-5] ERROR
org.apache.solr.client.solrj.impl.ConcurrentUpdateSolrServer - error
java.lang.Exception: Bad Request



SOLR 4.2.1 log error
======================================================
INFO: [mycore] webapp=/solr path=/update params={} {} 0 0
May 6, 2013 6:13:55 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: Missing ContentType
        at
org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:78)
        at
org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
        at
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
        at org.apache.solr.core.SolrCore.execute(SolrCore.java:1817)
        at
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:639)
        at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:345)
        at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:141)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
        at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
        at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:679)



I have other SolrJ clients using the 3.6 Solr jars and CommonsHttpSolrServer
to index to SOLR 4.2.1 with no problem, the issue seems to be with
ConcurrentUpdateSolrServer.

UpdateRequestHandler.java seems to be the source of the error.
<https://svn.apache.org/repos/asf/lucene/dev/trunk/solr/core/src/java/org/apache/solr/handler/UpdateRequestHandler.java>
  

I'm wondering if the issue is with the 4.3.1 solrconfig settings for the
/update date handler, currently just 

     <requestHandler name="/update" class="solr.UpdateRequestHandler"/>

Also my ConcurrentUpdateSolrServer constructor does not specify an http
client, I made a few failed attempts at setting content type that way.

any help appreciated!

DK



--
View this message in context: 
http://lucene.472066.n3.nabble.com/ConcurrentUpdateSolrServer-Missing-ContentType-error-on-SOLR-4-2-1-tp4061160.html
Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to