Getting error when connecting to Repository to RTC 6.0.3
Getting error when connecting to Repository. It is RTC 6.0.3
!ENTRY com.ibm.team.process.rcp.ui 4 0 2017-06-20 13:27:24.821
!MESSAGE Error logged from Process RCP UI:
!STACK 0
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ2384E Cannot connect to the repository at URL "https://XXXXXXXXXX:9445/jazz", 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: Remote host closed connection during handshake
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:314)
at com.ibm.jsse2.SSLSocketImpl.h(SSLSocketImpl.java:691)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:32)
at com.ibm.jsse2.SSLSocketImpl.startHandshake(SSLSocketImpl.java:307)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:57)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:31)
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
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at com.ibm.jsse2.c.a(c.java:14)
at com.ibm.jsse2.SSLSocketImpl.a(SSLSocketImpl.java:852)
... 13 more
One answer
It's an SSL handshake error, which means that the RTC client is not configured correctly for the SSL setting of the server. One common cause is that the server is restricted to TLSv1.2 only but the client is not configured for that. But without any further information, it will be difficult to say what is the exact cause.
You can either do an SSL tracing on the client side to check the detailed information about the SSL handshake, or use Wireshark to capture the packets and analyze the same thing. If you don't know how to do it, contact IBM Support.
https://jazz.net/wiki/bin/view/Deployment/IntegrationsTroubleshootingSmartCardDebug#Debug_Trace_for_IBM_Rational_AN1