[
https://issues.jenkins-ci.org/browse/JENKINS-9233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163696#comment-163696
]
Christoph Gysin commented on JENKINS-9233:
------------------------------------------
I'd like to look into this, but so far I failed to reproduce the issue.
I'm using:
jenkins master
jabber-plugin master
prosody-0.8.2
I have set up a test build that waits 20 seconds, then tries to send a XMPP
notification. Before the build completes I'd like to simulate a non-responding
XMPP server. When I send prosody SIGKILL, jenkins notices that the connection
has closed. If I send it a SIGSTOP, jenkins doesn't report any error on sending
the notification.
Any idea how to reproduce this behaviour?
> Builds hang on jabber notification when XMPP server is not responding
> ---------------------------------------------------------------------
>
> Key: JENKINS-9233
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9233
> Project: Jenkins
> Issue Type: Bug
> Components: jabber
> Reporter: kutzi
> Assignee: kutzi
>
> We had the problem that all our builds did hang, because the XMPP server was
> not responding (it had an OOME)
--
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
