Jenkins RTC Error - Unrecognized SSL message, plaintext connection
Failed to connect : CRJAZ0099E An HTTP error occurred when this URL was being accessed: /ccm/versionCompatibility?clientVersion=6.0.2. Error details: Unrecognized SSL message, plaintext connection?.
Failed to connect : CRJAZ0099E An HTTP error occurred when this URL was being accessed: /ccm/versionCompatibility?clientVersion=6.0.2. Error details: Unrecognized SSL message, plaintext connection?. com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: /ccm/versionCompatibility?clientVersion=6.0.2. Error details: Unrecognized SSL message, plaintext connection?. at com.ibm.team.repository.transport.client.RemoteTeamServer.executePrimitiveRequest(RemoteTeamServer.java:1918) at com.ibm.team.repository.transport.client.RemoteTeamServer.executeWithAuthHandling(RemoteTeamServer.java:1546) at com.ibm.team.repository.transport.client.RemoteTeamServer.executeMethod(RemoteTeamServer.java:1172) at
2 answers
You're not supposed to change anything on the RTC server if it is working fine with web browsers and the Eclipse client. The error message suggests that your Jenkins server has problems with going through the proxy server. Have you checked out this post?
https://jazz.net/forum/questions/214230/how-do-you-configure-jenkins-to-work-with-a-proxy-server
Additional to the -Dhttp.proxyHost and -Dhttp.proxyPort options, you may need to add -Dhttps.proxyHost and -Dhttps.proxyPort as well.
Comments
I have configured four proxy parameters
Of course it's related to SSL configuration, but it's not the Jenkins is expected encrypted responses - SSL is encrypted anyway. The error basically means that an SSL connection cannot be established.
As you keeps saying Jenkins server, are you really sure the error is thrown by the Jenkins server, not the Jenkins slaves? You need to make the same SSL configuration on all Jenkins machines, be it server or slave.
I have only one Jenkins server. There is no slave.
I can't think of anything else at the moment. If you know how to capture and analyze network trace, you can do it to find out why the error is thrown. Otherwise, contact IBM Support and get some assistance there.
This looks like a network error and not like an RTC problem. On the Jenkins host, make sure you can reach
Comments
Hi Ralph,