OutOfMemory or Poor Performance due to XML View of a Filter
Symptoms
JIRA slows down or performs poorly or hits an Out of Memory Exception. The following types of threads are in the thread dump:
Please note that the appearance of this thread in a thread dump may not be problematic; it's a normal function of JIRA and may be disregarded if there are no performance problems.
"http-9081-Processor263" daemon prio=1 tid=0x0000002b334e00e0 nid=0x25a7 runnable [0x0000000050351000..0x0000000050353e30]
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable. (Throwable.java:181)
at java.lang.Exception. (Exception.java:29)
at org.apache.tomcat.dbcp.dbcp.AbandonedTrace.setStackTrace(AbandonedTrace.java:160)
at org.apache.tomcat.dbcp.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:86)
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at org.ofbiz.core.entity.transaction.JNDIFactory.getJndiConnection(JNDIFactory.java:168)
at org.ofbiz.core.entity.transaction.JNDIFactory.getConnection(JNDIFactory.java:140)
...
at com.atlassian.jira.issue.views.SearchRequestXMLView.writeSearchResults(SearchRequestXMLView.java:77)
The important line is:
com.atlassian.jira.issue.views.SearchRequestXMLView.writeSearchResults
Cause
XML rendering is required for Displaying Search Results in XML. One common use is the jiraissues macro in Confluence. In a large instance, this can cause poor performance because the results are not paged and require XML transformation.
Resolution
Change the jira.search.views.max.limit parameter. Make sure to do this one, rather than the default max limit. See Limiting the number of issues returned from a search view such as an RSS feed.
Also, the following Feature Request was created to improve the performance of XML rendering on Jira: JRASERVER-20346 - Getting issue details... STATUS