![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
kutzi
|
|
Attachments:
|
jabber-plugin-stacktrace.txt |
|
Components:
|
jabber-plugin |
|
Created:
|
30/Apr/15 11:10 AM
|
|
Description:
|
We're migrating to Jenkins from Hudson. On Hudson we ran with version 22 of the Jabber plugin. Now, with the migration to Jenkins, we cannot connect to our corporate Jabber server anymore that requires legacy SSL enabled. With a plain connection, our Jabber server is not responding at all. Thus smack throws a org.jivesoftware.smack.SmackException$NoResponseException.
As the exception handler in hudson.plugins.jabber.im.transport.JabberIMConnection.createConnection doesn't set retryWithLegacySSL to true, there won't be an attempt to connect via legacy SSL, leading to a complete failure of the plugin for us.
|
|
Environment:
|
Jenkins 1.611, instant-messaging plugin 1.34, japper-plugin 1.34
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugins
jabber
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Florian Wiesner
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
