lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance Norskog (JIRA)" <>
Subject [jira] Commented: (SOLR-1413) Add MockSolrServer to SolrJ client tests
Date Tue, 08 Sep 2009 03:26:58 GMT


Lance Norskog commented on SOLR-1413:


In fact I'm now afraid it won't work, I don't know java HTTP coding ver well. Are HTTP sessions
are matched between threads in the SolrJ client app and servlet HTTP sessions?

That is, if 8 client threads walk the same sequence of mock responses, will the Apache Commons
simple and multi-threaded connection managers vector the client threads to the right sessions?
If not, the clients will get a random sequence of responses and some of the sessions will
run out of responses.

Do I have to turn on something in the Servlet?

> Add MockSolrServer to SolrJ client tests
> ----------------------------------------
>                 Key: SOLR-1413
>                 URL:
>             Project: Solr
>          Issue Type: Test
>          Components: clients - java
>         Environment: Any Solr distribution. Uses only the SolrJ client code, nothing
in the Solr core.
>            Reporter: Lance Norskog
>            Priority: Minor
>         Attachments: SOLR-1413.patch, SOLR-1413.patch
> The SolrJ unit test suite has no "mock" solr server for HTTP access, and there are no
low-level tests of the Solrj HTTP wire protocols.
> This patch includes and
The mock server does not parse its input and responds with pre-configured byte streams. The
latter does a few tests in the XML wire format. Most of the tests do one request and set up
success and failure responses.
> Unfortunately, there is a bug: I could not get 2 successive requests to work. The mock
server's TCP socket does not work when reading the second request.  If someone who knows the
JDK socket classes could look at the mock server, I would greatly appreciate it.
> The alternative is to steal a bunch of files from the apache commons httpclient test
suite. This is a quite sophisticate bunch of code:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message