Exalate had troubles communicating with the remote side when polling for changes, the communication will be retried automatically

Originally asked by Ankush Kumar on 02 July 2020 (original question)


com.exalate.api.exception.network.jiranode.SslAvailabilityNetworkException: Problems related to SSL certificate. Contact your system administrator. Detailes: `Certificate for doesn’t match any of the subject alternative names: [api.knowunity.de]`. at com.exalate.node.error.JiranodeAvailabilityNetworkExceptionCategoryService.generateSslAvailabilityNetworkException(JiranodeAvailabilityNetworkExceptionCategoryService.java:169) at com.exalate.transport.rest.client.v1.RestTransportProtocol.retry(RestTransportProtocol.java:447) at com.exalate.transport.rest.client.v1.RestTransportProtocol.pollSyncRequests(RestTransportProtocol.java:268) at com.exalate.transport.TransportService.pollSyncRequests(TransportService.java:155) at com.exalate.replication.in.PollerService.pollSyncRequests(PollerService.java:104) at com.exalate.replication.in.PollerService.pollPrivateConnections(PollerService.java:80) at com.exalate.replication.in.PollRequestWorker$1.run(PollRequestWorker.java:30) at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService$1.run(ClusteredSensitiveExecutorService.java:32) at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService$1.run(ClusteredSensitiveExecutorService.java:28) at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService.executeHandlingLocks(ClusteredSensitiveExecutorService.java:54) at com.exalate.node.util.concurrent.ClusteredSensitiveExecutorService.executeHandlingLocks(ClusteredSensitiveExecutorService.java:28) at com.exalate.replication.in.PollRequestWorker.run(PollRequestWorker.java:26) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: javax.net.ssl.SSLPeerUnverifiedException: Certificate for doesn’t match any of the subject alternative names: [api.knowunity.de] at org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:467) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:397) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:105) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:131) at sun.reflect.GeneratedMethodAccessor551.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.atlassian.plugins.rest.module.ContextClassLoaderSwitchingProxy.invoke(ContextClassLoaderSwitchingProxy.java:22) at com.sun.proxy.$Proxy3724.executeAndReturn(Unknown Source) at sun.reflect.GeneratedMethodAccessor551.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.exalate.transport.rest.client.loggingproxy.HttpRequestLoggingProxy.invokeMethodWithArgs(HttpRequestLoggingProxy.java:161) at com.exalate.transport.rest.client.loggingproxy.HttpRequestLoggingProxy.invoke(HttpRequestLoggingProxy.java:95) at com.sun.proxy.$Proxy3724.executeAndReturn(Unknown Source) at com.exalate.transport.rest.client.v4_1.ConnectionPollClient.executeAndReturn(ConnectionPollClient.java:226) at com.exalate.transport.rest.client.v4_1.ConnectionPollClient.pollSyncRequests(ConnectionPollClient.java:63) at com.exalate.transport.rest.client.v1.RestTransportProtocol$11.call(RestTransportProtocol.java:271) at com.exalate.transport.rest.client.v1.RestTransportProtocol$11.call(RestTransportProtocol.java:268) at com.exalate.transport.rest.client.v1.RestTransportProtocol.retry(RestTransportProtocol.java:437) … 17 more


Answer by Francis Martens (Exalate) on 02 July 2020

Ankush Kumar

Can you validate that all the endpoints have a valid ssl certificate. You can test this with https://ssllabs.com

Let me know