Problem Definition

Currently JIRA/Tomcat doesn't have information about URI in Java thread name (Tomcat worker). This makes troubleshooting of performance problems more complicated, as it hard to get thread from URL and other way around.

Suggested Solution

Rename Java thread name and add URI, so it will look like:

"http-bio-127.0.0.1-8080-exec-355, unique_id=Vp, time=1453, uri=/jira/browse/TEST/" daemon prio=10 tid=0x00002b0cd18f0800 nid=0x13ac runnable [0x00002b0cdad94000]
   java.lang.Thread.State: RUNNABLE

See sample filter for Tomcat, example: http://stackoverflow.com/questions/14058233/naming-tomcat-worker-threads

Workaround

Use Thready plugin, it will add URL and User to thread name, so it will provide us extra information on the thread dump generation.

2016-10-25 13:32:35,081 http-nio-8080-exec-243 uri:/secure/admin/views/issuefields/screens/viewfieldscreens.jsp username:admin ERROR admin 806x861289x78 82gnu5 1.1.1.1 /secure/admin/ViewFieldScreens.jspa [webwork.util.ValueStack] METHOD: "deletable", exception: 
java.lang.IllegalArgumentException: Cannot find Screen with id '15608'.
	at com.atlassian.jira.workflow.WorkflowActionsBean.getFieldScreenForView(WorkflowActionsBean.java:73) [jira-api-7.2.2.jar:?]

Fix

New version of ATST 1.32.1 contains Thready functionality , see ATST version-history

If Jira is experiencing problems, Atlassian Support may ask for a set of thread dumps to help diagnose the problem. We now include the user ID and request URL in thread names, which can help us identify and troubleshoot issues faster.