[
https://issues.jenkins-ci.org/browse/JENKINS-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160142#comment-160142
]
Oliver Walsh commented on JENKINS-11859:
----------------------------------------
Working with jenkins 1.452 & urltrigger 0.14.
Thanks,
Ollie
> "java.io.IOException: Stream closed" when monitoring a jenkins job build
> number
> -------------------------------------------------------------------------------
>
> Key: JENKINS-11859
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11859
> Project: Jenkins
> Issue Type: Bug
> Components: urltrigger, xtrigger
> Affects Versions: current
> Reporter: Oliver Walsh
> Assignee: gbois
> Priority: Minor
> Attachments: config.xml, config.xml
>
>
> I have a URL trigger on jenkins server A (v1.439) setup to monitor the build
> number of job on jenkins server B (v1.437).
> This is the URL trigger log:
> {noformat}
> Polling started on Nov 24, 2011 9:46:30 AM
> Invoking the url:
> http://<jenkinsB>/job/<somejob>/lastSuccessfulBuild/buildNumber
> Inspecting the content
> The line '124' matches the pattern '[0-9]+'
> [ERROR] - SEVERE - Polling error java.io.IOException: Stream closed
> {noformat}
> This is the response header for the url when viewing it in chrome debugger:
> {noformat}
> HTTP/1.1 200 OK
> Server: Winstone Servlet Engine v0.9.10
> Content-Type: text/plain;charset=US-ASCII
> Connection: Close
> Date: Thu, 24 Nov 2011 10:11:31 GMT
> X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
> {noformat}
> I can workaround this by using the api url to fetch the build number
> http://<jenkinsB>/job/<somejob>/lastSuccessfulBuild/api/xml?xpath=string(*/number)
> which does not close the connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
