RTC tool access RTC failed through HTTPS
!ENTRY com.ibm.team.repository.client 1 800 2017-05-16 11:06:12.827
!MESSAGE CRJAZ0053I The identifier for the repository identified by "https://xxx/ccm" could not be contacted: Received fatal alert: handshake_failure
!STACK 0
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.j.a(j.java:15)
at com.ibm.jsse2.j.a(j.java:39)
at com.ibm.jsse2.qc.b(qc.java:820)
at com.ibm.jsse2.qc.a(qc.java:25)
at com.ibm.jsse2.qc.h(qc.java:634)
at com.ibm.jsse2.qc.a(qc.java:827)
at com.ibm.jsse2.qc.startHandshake(qc.java:451)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:55)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:14)
at com.ibm.net.ssl.www2.protocol.https.b.connect(b.java:16)
at com.ibm.team.repository.client.util.RepositoryUtil.getRepositoryId2(RepositoryUtil.java:115)
at com.ibm.team.repository.client.internal.TeamRepositoryService.connectToAndUpdateTeamRepository(TeamRepositoryService.java:401)
at com.ibm.team.repository.client.internal.TeamRepositoryService.getTeamRepositoryWithOverride(TeamRepositoryService.java:180)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage.createNewRepository(RepositoryCreationPage.java:235)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage.create(RepositoryCreationPage.java:201)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage$1.run(RepositoryCreationPage.java:130)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!ENTRY com.ibm.team.process.rcp.ui 4 0 2017-05-16 11:06:12.827
!MESSAGE Error logged from Process RCP UI:
!STACK 0
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ2384E Cannot connect to the repository at URL "https://xxx/ccm", see the nested exception for more details.
at com.ibm.team.repository.client.util.RepositoryUtil.getRepositoryId2(RepositoryUtil.java:139)
at com.ibm.team.repository.client.internal.TeamRepositoryService.connectToAndUpdateTeamRepository(TeamRepositoryService.java:401)
at com.ibm.team.repository.client.internal.TeamRepositoryService.getTeamRepositoryWithOverride(TeamRepositoryService.java:180)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage.createNewRepository(RepositoryCreationPage.java:235)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage.create(RepositoryCreationPage.java:201)
at com.ibm.team.process.rcp.ui.RepositoryCreationPage$1.run(RepositoryCreationPage.java:130)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at com.ibm.jsse2.j.a(j.java:15)
at com.ibm.jsse2.j.a(j.java:39)
at com.ibm.jsse2.qc.b(qc.java:820)
at com.ibm.jsse2.qc.a(qc.java:25)
at com.ibm.jsse2.qc.h(qc.java:634)
at com.ibm.jsse2.qc.a(qc.java:827)
at com.ibm.jsse2.qc.startHandshake(qc.java:451)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:55)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:14)
at com.ibm.net.ssl.www2.protocol.https.b.connect(b.java:16)
at com.ibm.team.repository.client.util.RepositoryUtil.getRepositoryId2(RepositoryUtil.java:115)
... 6 more
One answer
You're probably going to need a recent Java 6 or even Java 7 or 8 as your -vm. In addition you will have to add another entry in Eclipse.ini. I installed Java 8 in c:\java8 and change eclipse.ini thus ( just the bold lines ). There will be something there after -vm, replace with the location of your updated JRE ( try not to put in "Program Files" that's more pain than it's worth )
-vm
c:\java8\jre\bin
--launcher.XXMaxPermSize
256m
-vmargs
-Xdump:system:events=systhrow,filter=java/lang/OutOfMemoryError,request=exclusive+prepwalk
-Xms100m
-Xmx512m
-Dosgi.requiredJavaVersion=1.6
-Dosgi.bundlefile.limit=100
-Djavax.xml.accessExternalSchema=platform,file
-Dcom.ibm.team.repository.transport.client.protocol=SSL_TLSv2
I had the last bold line in the eclipse.ini prior to upgrading Java and the RTC login wasn't failing so much as not trying very hard and emitting no failures. It wasn't until I pointed to newer Java that the client worked. (heritage: RTC 6.0.2 OOTB from ZIP install )
Comments
Donald Nong
May 17 '17, 1:59 a.m.More information is needed. How does "Eclipse Luna" work fine? Does it have RTC plugin installed together? Is your RTC server support TLSv1.2 only?
Ee Chian Jeremy Chu
May 17 '17, 2:32 a.m.SSLProtocolDisable SSLv2 SSLv3 TLSv1 TLSv1.1
SSLCipherSpec ALL -SSL_RSA_WITH_RC4_128_MD5