Summary

From investigating PS-7804 JIRA hits OOME because user create board with empty filter that load all issues in the instance and dump into the memory. JIRA eventually hit OOME when user accesses this board repeatedly.

Environment

• Large instance with > 1M issues

Steps to Reproduce

1. generate 1M issues
2. create Agile board with empty board filter
3. load this board repeatedly

Expected Results

1. there should be a limit of issues can be loaded in a single board
2. there should be a validation check for creating board with empty filter 

Actual Results

• JIRA hits OOME

Note

• For this fix to work you need to set "Disable empty JQL queries set" to ON.
• Please note that fix in JRASERVER-65602 would partially fix the current problem. This is due to the fact that when Agile executes the board's JQL it adds additional parameters to query so, JQL becomes "not empty" (see JRASERVER-67409).

Workaround

• Use the following SQL to list boards with empty filter

   SELECT * FROM "AO_60DB71_RAPIDVIEW" WHERE "SAVED_FILTER_ID" IN (SELECT id FROM searchrequest WHERE reqcontent = '');
  

• To avoid loading the board directly, modify the ID in the request call below to bring you to its configuration page where you can modify the JQL in use:
  https://yourdomain.com/secure/RapidView.jspa?rapidView=5791&tab=filter|