|
||||||||
|
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/d/optout.
No, that is not what we are seeing in this issue. The exception is catched and logged by https://github.com/jenkinsci/jabber-plugin/blob/master/src/main/java/hudson/plugins/jabber/im/transport/JabberIMConnection.java#L540
As I tried to explain: There is no evidence that the XMPPException thrown by createVCard is causing the connection termination. In fact the termination as shown in the log happens 10 minutes after the exception is thrown. I guess you are a bit biased towards vcard because of
JENKINS-25515.With the information the issue currenctly contains, it's not even clear which side, client or server, sends the closing stream element first, i.e. terminates the stream.