I have found a workaround for this.
1. change the entry in solrconfig.xml for the DataImportHandler by removing
the slash from the name, like this <requestHandler name="dataimport"...
2. when making the request to the SolrJ server, don't use a slash in the qt
parameter, i.e.
solrParameters.set("qt", "dataimport");
If you use slashes, the url generated by SolrJ will be like
'/solr/dataimport...&qt=%2Fdataimport'
Removing the slashes will change the url to something like
'/solr/select...&qt=dataimport'
(Solr will use the 'qt' parameter to find the right handler).
The resulting url will be something like this:
/solr/select?optimize=true&clean=false&commit=true&command=reload-config&qt=dataimport&wt=javabin&version=1
My guess is that '/select' is mapped in the web.xml of Solr to a servlet,
whereas '/dataimport' is not and that Websphere will complain about that,
whereas JBoss doesn't care.
--
View this message in context:
http://lucene.472066.n3.nabble.com/DataImportHandler-on-Websphere-http-response-404-tp2240440p2242162.html
Sent from the Solr - User mailing list archive at Nabble.com.
