Error rendering Activity tab on Jira Issue view
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The following error appears on a Jira issue screen, in place where Activity tab should be displayed:
Error rendering 'com.atlassian.jira.jira-view-issue-plugin:activitymodule'. Please contact your Jira administrators.
Environment
Jira 9.x
Diagnosis
In atlassian-jira.log file, the following error is observed:
1
2
3
4
5
6
7
8
9
10
2025-01-22 10:13:19,364+0400 http-nio-8080-exec-26 ERROR admin 613x6747058x1 1hd66n4 127.0.0.1,192.168.1.2 /browse/TEST-58 [c.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: com.atlassian.templaterenderer.RenderingException: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.streams.jira.portlet.ActivityStreamIssueTab$1 threw exception com.atlassian.gadgets.GadgetParsingException: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 403 at viewissue/activityblock.vm[line 78, column 31]
com.atlassian.templaterenderer.RenderingException: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.streams.jira.portlet.ActivityStreamIssueTab$1 threw exception com.atlassian.gadgets.GadgetParsingException: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 403 at viewissue/activityblock.vm[line 78, column 31]
at com.atlassian.templaterenderer.velocity.one.six.internal.VelocityTemplateRendererImpl.render(VelocityTemplateRendererImpl.java:129)
at com.atlassian.templaterenderer.velocity.AbstractCachingWebPanelRenderer.render(AbstractCachingWebPanelRenderer.java:48)
at com.atlassian.plugin.web.model.ResourceTemplateWebPanel.writeHtml(ResourceTemplateWebPanel.java:45)
at com.atlassian.plugin.web.model.ResourceTemplateWebPanel.getHtml(ResourceTemplateWebPanel.java:56)
at com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel.getHtml(DefaultWebPanelModuleDescriptor.java:127)
at com.atlassian.jira.plugin.issuenav.IssueNavAction.renderActivityModule(IssueNavAction.java:710)
at jdk.internal.reflect.GeneratedMethodAccessor65101.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)Furthermore, we see a different warning related to the one above:
1
2025-01-22 10:13:07,257+0400 http-nio-8080-exec-27 WARN admin 613x6747001x1 1hd66n4 127.0.0.1,192.168.1.2 /browse/TEST-58 [c.a.g.r.internal.http.HttpClientFetcher] A request to https://my.server.com/rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin/gadgets/activitystream-gadget.xml has been denied. To allow requests to this URL add the application URL to your whitelist (http://confluence.atlassian.com/x/KQfCDQ).Gadget feed health check is failing:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
2025-01-22 10:15:02,073+0400 HealthCheck:thread-4 ERROR [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.ConnectTimeoutException: Connect to my.server.com:80 [my.server.com/192.168.1.2] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck.check(GadgetFeedUrlHealthCheck.java:62)Cause
There is a mismatch between the URL users are accessing Jira through and the base URL or Tomcat connector configuration. For example:
Jira base URL indicates a secure HTTPS protocol (e.g. https://my.server.com)
Tomcat connector is configured with proxy parameters using secure HTTPS and port:
proxyName="my.server.com" proxyPort="443" scheme="https"However, users are accessing Jira via HTTP protocol (e.g. http://my.server.com)
Other combinations of HTTP and HTTPS being used in some of those cases are also possible.
Solution
Tomcat connector configuration, Jira base URL and the URL users are using to access Jira must be consistent: all these elements must either define usage of HTTP or HTTPS exclusively.
For example, if your environment uses secure HTTPS URL to access Jira:
Base URL must contain the corresponding HTTPS URL (e.g. https://my.server.com)
Tomcat connector must be configured with proxy parameters using secure HTTPS and port:
proxyName="my.server.com" proxyPort="443" scheme="https"Jira users must be accessing Jira through the base URL (https://my.server.com)
Reverse-proxy / load balancer must publish
my.server.comname on port 443
Was this helpful?