Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
3
-
Severity 2 - Major
-
1
-
Description
Issue Summary
Jira chart Macro timeout to render on Confluence cloud and Jira Server instance
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Connect application link to Jira Server
- Create a page in confluence
- Add Jira chart macro
Expected Results
chart to display results on confluence page
Actual Results
Macro fails to load and page errors as well
WARN: message: Caching error: JiraRuntimeException: Bypassing caching for Jira Columns List, since Jira Columns Info list doesn't include custom field
-----
org.apache.http.conn.ConnectTimeoutException: Connect to jira-api.netflix.net:443 [jira-api.netflix.net/44.236.228.55, jira-api.netflix.net/44.239.18.172, jira-api.netflix.net/52.42.207.38] failed: connect timed out
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
com.atlassian.confluence.util.http.httpclient.InstrumentedPoolingConnectionManager.connect(InstrumentedPoolingConnectionManager.java:47)
org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
com.atlassian.confluence.util.http.httpclient.InstrumentedHttpClientBuilder.lambda$createHttpBuilder$0(InstrumentedHttpClientBuilder.java:189)
brave.httpclient.TracingMainExec.execute(TracingMainExec.java:50)
org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
brave.httpclient.TracingProtocolExec.execute(TracingProtocolExec.java:41)
org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.getDataForSingleApplink(JiraAggregateProvider.java:138)
com.atlassian.confluence.plugins.metadata.jira.aggregate.JiraAggregateProvider.lambda$getAggregateData$0(JiraAggregateProvider.java:122)
com.atlassian.workcontext.api.WorkContextFunctionWrapper.lambda$withContext$2(WorkContextFunctionWrapper.java:65)
com.atlassian.workcontext.api.WorkContextFunctionWrapper.lambda$withContext$7(WorkContextFunctionWrapper.java:118)
com.atlassian.workcontext.api.WorkContextFunctionWrapper.lambda$withContext$3(WorkContextFunctionWrapper.java:74)
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.net.SocketTimeoutException: connect timed out
java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412)
java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255)
java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237)
java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
java.base/java.net.Socket.connect(Socket.java:609)
org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368)
org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
... 21 more
}
ext: { [+]
}
hostname: 3612f9be9e06
level: ERROR
logger: com.atlassian.confluence.plugins.metadata.jira.helper.JiraMetadataErrorHelper
m: { [+]
}
message: Unknown error encountered while retrieving Jira metadata. Please check the logs.
Confluence Cloud is making connections from unpublished ranges. Our documentation is wrong. This is due to that fact that Confluence Cloud has not yet adopted our "single egress" platform for making outgoing calls. This means Confluence Cloud outgoing connections can come from potentially any EC2 IP.
Workaround
Using Application Tunnels is a potential solution.