|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15601) Main das... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)
- [JIRA] (JENKINS-15601) Mai... [email protected] (JIRA)

I think that the message/error in the log is a symptom of the problem and not the problem itself. It looks like the client (web browser) has given up waiting and has closed the connection.
This explains the exception messages: "Failed to write to client" and "Caused by: java.net.SocketException: Broken pipe".