-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
On a system with about 300 boards, it takes about 30 seconds for the the link View On Board to return a result.
Diagnosis
When reviewing thread dumps (as per Troubleshooting Performance Issues with Thread Dumps) taking during slow performance, the below stack traces can be found:
"http-bio-8080-exec-8436" daemon prio=10 tid=0x00007f22dd940000 nid=0x6f6a runnable [0x00007f26184c5000] java.lang.Thread.State: RUNNABLE at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:240) at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:209) at org.apache.lucene.index.SegmentReader.docFreq(SegmentReader.java:503) at org.apache.lucene.search.TermQuery$TermWeight$1.add(TermQuery.java:56) at org.apache.lucene.util.ReaderUtil$Gather.run(ReaderUtil.java:77) at org.apache.lucene.util.ReaderUtil$Gather.run(ReaderUtil.java:82) at org.apache.lucene.util.ReaderUtil$Gather.run(ReaderUtil.java:66) at org.apache.lucene.search.TermQuery$TermWeight.<init>(TermQuery.java:53) at org.apache.lucene.search.TermQuery.createWeight(TermQuery.java:198) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.BooleanQuery$BooleanWeight.<init>(BooleanQuery.java:176) at org.apache.lucene.search.BooleanQuery.createWeight(BooleanQuery.java:354) at org.apache.lucene.search.Searcher.createNormalizedWeight(Searcher.java:168) at org.apache.lucene.search.IndexSearcher.createNormalizedWeight(IndexSearcher.java:661) at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:320) at com.atlassian.jira.index.DelegateSearcher.search(DelegateSearcher.java:153) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.getHitCount(LuceneSearchProvider.java:247) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.searchCountOverrideSecurity(LuceneSearchProvider.java:129) at sun.reflect.GeneratedMethodAccessor1832.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) at com.sun.proxy.$Proxy229.searchCountOverrideSecurity(Unknown Source) at sun.reflect.GeneratedMethodAccessor1832.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at com.sun.proxy.$Proxy229.searchCountOverrideSecurity(Unknown Source) at com.atlassian.greenhopper.issue.index.FindQueriesMatchingIssueAdapter.findQueries(FindQueriesMatchingIssueAdapter.java:37) at com.atlassian.greenhopper.issue.index.DefaultFindQueriesMatchingIssueAdapter.findQueries(DefaultFindQueriesMatchingIssueAdapter.java:26) at com.atlassian.greenhopper.service.issue.SearchServiceImpl.findQueriesMatchingIssue(SearchServiceImpl.java:105) at com.atlassian.greenhopper.service.rapid.RapidViewLocationServiceImpl.findQueriesMatchingIssue(RapidViewLocationServiceImpl.java:371) at com.atlassian.greenhopper.service.rapid.RapidViewLocationServiceImpl.getRapidViewsForIssue(RapidViewLocationServiceImpl.java:158) at com.atlassian.greenhopper.web.rapid.RapidViewLocationResolverFactory$IssueRapidViewLocationResolver.getRapidViewsForObject(RapidViewLocationResolverFactory.java:155) at com.atlassian.greenhopper.web.rapid.RapidViewLocationResolverFactory$IssueRapidViewLocationResolver.getRapidViewsForObject(RapidViewLocationResolverFactory.java:131) at com.atlassian.greenhopper.web.rapid.BoardDispatchAction._doGoToBoard(BoardDispatchAction.java:115) at com.atlassian.greenhopper.web.rapid.BoardDispatchAction.doGoToBoard(BoardDispatchAction.java:56) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source)
Workaround:
Go to Administration > Add-Ons > Manage Add-Ons > JIRA Agile and disable greenhopper-agile-issue-web-panel to prevent display of this link. This will dissuade users from using this feature.
- is duplicated by
-
JSWSERVER-8101 GHGoToBoard slow on JAC
-
- Closed
-
-
- Closed
- is related to
-
- Gathering Interest
-
JDEV-29434 Failed to load
- relates to
-
- Closed
-
- Closed
- is cloned by
-
JDEV-29431 Loading...
[JSWSERVER-8775] View on Board operation slow with large amount of boards
Thanks Pawel. I'm seeing the same error for all links in the Agile panel on my issues. Is the Agile panel in 6.6.0 only compatible with Jira 6.4+? Marketplace claims 6.6.0 will work with Jira 6.1-6.3.6.
hmm, I'm not seeing this "fixed" on Jira 6.2.3+Agile 6.6. See screenshot
This is currently open as the fix for JIRA was buggy and I've just fixed it. I know that this was also temporarily disabled in Agile due to OD fuck up caused by my changes. Going to close it when I merge JIRA fix and restore Agile to use it.
Daniel, it's been a while so I don't recall exactly what it's doing. The workaround here didn't work for us either. Instead, we opted to hide the link via javascript in the Announcement Banner:
<style type="text/css">
.js-rapidboard-operation-issue{
display:none;
}
</style>
hat-tip to @nmuldoon for the suggestion.
There's one more area users can still get to this slow operation under More > Agile Board. To hide that, we're experimenting with disabling the plugin module: greenhopper-rapidboard-operation.
Daniel Lai
added a comment - By the way, disabling the greenhopper-agile-issue-web-panel module removes the entire Agile section from the issue detail page. This will also hide any Sprint link, which works fine and doesn't have any performance issue.
Daniel Lai
added a comment - By the way, disabling the greenhopper-agile-issue-web-panel module removes the entire Agile section from the issue detail page. This will also hide any Sprint link, which works fine and doesn't have any performance issue. We're on Jira 6.0.8 / Jira Agile 6.3.5 and are also having a problem with the View on Board link not working and resulting in the Communications Breakdown error after several minutes. We have 1000+ boards in our instance. But the open in new window workaround on the link doesn't work and just shows an empty page with the jira header at the top.
@David Yu, was wondering how did you tell that every single board's JQL is being executed when clicking the link? I turned on SQL logging in Jira and I saw a bunch of queries like the following on different IDs, but there were only about 30 such queries.
2014-05-28 11:32:38,521 http-bio-8080-exec-23 admin 692x1371x1 1myzgy9 /secure/GHGoToBoard.jspa 1ms "SELECT filtername, authorname, DESCRIPTION, username, groupname,
projectid, reqcontent, FAV_COUNT, filtername_lower FROM searchrequest WHERE ID='10998'"
Daniel Lai
added a comment - - edited We're on Jira 6.0.8 / Jira Agile 6.3.5 and are also having a problem with the View on Board link not working and resulting in the Communications Breakdown error after several minutes. We have 1000+ boards in our instance. But the open in new window workaround on the link doesn't work and just shows an empty page with the jira header at the top.
@David Yu, was wondering how did you tell that every single board's JQL is being executed when clicking the link? I turned on SQL logging in Jira and I saw a bunch of queries like the following on different IDs, but there were only about 30 such queries.
2014-05-28 11:32:38,521 http-bio-8080-exec-23 admin 692x1371x1 1myzgy9 /secure/GHGoToBoard.jspa 1ms "SELECT filtername, authorname, DESCRIPTION, username, groupname,
projectid, reqcontent, FAV_COUNT, filtername_lower FROM searchrequest WHERE ID='10998'" Current client has 719 boards, upon clicking "View on Board" link, after about 2-3 minutes receive "Communication Breakdown" and in the browser developer console shows "ajax aborted". However I can get it to work 75% of the time by right clicking the "Agile Board" button and selecting "open in new window". 2-3 minutes later it shows the boards that the issue shows up on. Is there a way to configure ajax timeout to just not give up after 2-3 minutes of waiting for DB queries to finish?
Narendran Bhojan
added a comment - We have 739 Agile boards and this call takes 2-3 minutes to come back.
-Naren
Narendran Bhojan
added a comment - We have 739 Agile boards and this call takes 2-3 minutes to come back.
-Naren
thomas.jackson JIRA Agile 6.6.0 is compatible with JIRA 6.1+, but this performance gain will not be realised until you are running on JIRA 6.4.