[
https://issues.apache.org/jira/browse/NUTCH-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628754#comment-14628754
]
Peter Ciuffetti commented on NUTCH-2059:
----------------------------------------
Well, here's one theory. The HttpClient plugin test starts jetty servers at
fixed ports. Most tests use a port unique to the test. Some reuse a previous
port. It may be replated to parallel texting though possible more likely that
(due to another Jenkins job running on the same hist at the same time) that the
requested port is not available. The test makes no attempt to try another port
if the one it asks for is unavailable. This could be made more robust.
> protocol-httpclient, protocol-http unit test errors on Jenkins
> --------------------------------------------------------------
>
> Key: NUTCH-2059
> URL: https://issues.apache.org/jira/browse/NUTCH-2059
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Reporter: Peter Ciuffetti
> Assignee: Chris A. Mattmann
> Fix For: 1.11
>
>
> This is an occasional error on the build of the Nutch trunk visible in
> Jenkins builds. It happens on either protocol-http or protocol-httpclient,
> which can be running at the same time given the multi-threaded test setup.
> {code}
> [junit] Running org.apache.nutch.protocol.httpclient.TestProtocolHttpClient
> [junit] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.377
> sec
> [junit] Test org.apache.nutch.protocol.http.TestProtocolHttp FAILED
> {code}
> Evidence of failure on Jenkins go back to
> Failed > Console Output #3154 Jun 8, 2015 4:00:00 AM
> https://builds.apache.org/view/All/job/Nutch-trunk/3154/consoleFull
> And are repeated at...
> https://builds.apache.org/view/All/job/Nutch-trunk/3190/console
> https://builds.apache.org/view/All/job/Nutch-trunk/3189/console
> Some possibly related tickets
> NUTCH-1836 Timeouts in protocol-httpclient when crawling same host with >2
> threads
> NUTCH-1086 Rewrite protocol-httpclient
> The unit tests are not failing for me on my sandbox, but there are some
> exceptions being output to the log related to headers being sent on JSP pages
> after the response writer is invoked.
> {code}
> java.lang.IllegalStateException: STREAM
> at org.mortbay.jetty.Response.getWriter(Response.java:616)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
