You can now access JIRA through your web browser. I think the connection is building now successfully but there is a problem while starting the plug-ins as you can in the following see in the atlassian log: 09:50:45,694 -startStop-1 INFO The directory 'I:\Program Files\Atlassian\Application Data\JIRA' is validated and locked for exclusive use by this instance. I also worte the following in the connector: at .(HttpHelper.java:151)Īt .(HttpHelper.java:94)Īt .(HttpHelper.java:187)Īt .(HttpHelper.java:200)Īt .(HttpHelper.java:75)Īt .(MfactApiClient.java:361)Īt .(KExProcessorsProvider.java:368)Īt .(KExProcessorsProvider.java:1335)Īt .(KExProcessorsProvider.java:613)Īt .(KExProcessorsProvider.java:650)Īt .(KExProcessorsProvider.java:882)Īt .(PreparedImportStatus.java:156)Īt .ImportToolchainProjectFactory.lambda$1(ImportToolchainProjectFactory.java:166)Īt $LinkedValues.forEach(LinkedHashMap.java:608)Īt .ImportToolchainProjectFactory.importSourcesFromProject(ImportToolchainProjectFactory.java:162)Īt .ImportToolchainProjectFactory.importToolchainProject(ImportToolchainProjectFactory.java:366)Īt .(OpenMexForProject.java:129)Īt .$1(OpenMexForProject.java:185)Īt .ModalContext$n(ModalContext.java:122)Ĭaused by: : PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested targetĪt .doBuild(PKIXValidator.java:450)Īt .engineValidate(PKIXValidator.java:317)Īt .validate(Validator.java:262)Īt 509TrustManagerImpl.validate(X509TrustManagerImpl.java:330)Īt 509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:237)Īt 509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:132)Īt .serverCertificate(ClientHandshaker.java:1670)Ĭaused by: .SunCertPathBuilderException: unable to find valid certification path to requested targetĪt .SunCertPathBuilder.build(SunCertPathBuilder.java:141)Īt .SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)Īt .build(CertPathBuilder.java:280)Īt .doBuild(PKIXValidator.I have now configered the dbconfig.xml with ssl=true and replaced the jtds-1.3.1.jar file with another one to be able to do the SSLHandshake with TLSv1.2. at (HttpURLConnection.java:480)Īt sun.net. : : PKIX path building failed: .SunCertPathBuilderException: unable to find valid certification path to requested targetĪt .getSSLException(Alerts.java:198)Īt .fatal(SSLSocketImpl.java:1967)Īt .fatalSE(Handshaker.java:331)Īt .fatalSE(Handshaker.java:325)Īt .serverCertificate(ClientHandshaker.java:1688)Īt .processMessage(ClientHandshaker.java:226)Īt .processLoop(Handshaker.java:1082)Īt .process_record(Handshaker.java:1010)Īt .readRecord(SSLSocketImpl.java:1079)Īt .performInitialHandshake(SSLSocketImpl.java:1388)Īt .startHandshake(SSLSocketImpl.java:1416)Īt .startHandshake(SSLSocketImpl.java:1400)Īt sun.net. !MESSAGE getProcessor - server not available or other error #T5 handshaker installAn alternative is to find the JRE that the tool is using and install the certificates to the keystore for that JRE using the java keytool. #T5 handshaker androidAndroid Studio) is to install the certificates to the tools. The normal solution for this with other tools (e.g. I think that the problem is to do with the Thales UK coprorate proxy server using untrusted https certificates. Thanks for that link with instructions for locating the log file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |