|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
@hardwickj: this and the duplicate issue seem to be mixing up several things.
One is the issue reported in the summary, which is that a broken client connection results in a noisy stack trace in the Jenkins log file, which it should not, since this is a normal condition for an HTTP-based server application.
You report some 404s, which are probably some unrelated bug whose cause I cannot speculate on.
And others in
JENKINS-14825report extremely long delays in page loads under some circumstances. Such delays probably trigger this bug, but are caused by something unrelated—which may well be different in each case. Only a thread dump can diagnose why a page load is hanging.