Indexing problem, "400" Status: Bad Request
| Project: | Apache Solr Search Integration |
| Version: | 5.x-1.x-dev |
| Component: | SolrPHP Client |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm trying to test apache solr, but somehow I cannot get the indexing work. Whenever I try to run cron to update the index or delete the index, I always get the same response from the solr server: 400 Bad Request. I attached a raw TCP dump capture of a delete request. However, AFAICT the searches work albeit with empty results. Solr statistics counters in admin servlet gets updated. Any suggestions?
Details:
- Apache Solr nightly 11-Feb-2009, running on top of Tomcat 5.5 (also tested tomcat 6.0 with similar results)
- The 5.x-dev drupal module, dated 2009-Feb-04
- Solr can be pinged, the solr admin servlets seems to work
- Test site, no fancy modules, customizations, etc enabled.
- solr modules enabled: Apache Solr framework, Apache Solr search
The first few lines in tomcat logs of the exception are:
Feb 11, 2009 2:03:44 PM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: missing content stream
at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:49)
at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
| Attachment | Size |
|---|---|
| solr-request-trace.txt | 1.43 KB |
#1
I don't know how stable the 5 module is... But it looks like it might be a missing linebreak at the end of the XML payload? Totally random guess and I suppose unlikely.
Perhaps compare to the 6x version which is supported and see what differences exist in the payload?
#2
@skiminki,
Hi, are you still having problems with this?
If so, are you running Linux or Windows?
There may be something in the updated REAMDE.txt that helps, please see:
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/apachesolr/...
#3
This is no longer an important issue to us. Back then when I reported this, we eventually decided to postpone utilizing this module until we migrate the site in concern into newer version of Drupal. But anyhow, we're running Linux.
#4
Hi Jacob,
I'm experiencing the same problem
centos-5.3
tomcat-5.5-28
java-1.6.0
and (unfortunantly) drupal-5.20
on a 64 bit machine.
What does the "XML payload" mean? so I can start checking alongside the same issues.
The problem surfaces initially while trying to connect to the solr server.
I can telnet to the port in the machine serving so I assume this is not a connectivity issue.
Any help would be appreciated..