'Page Unavailable' Error When Associating Security Scheme to Large Number of Issues

Summary

When a user attempts to associate a new Issue Security Scheme to a large number of issues in a project (in tested cases, upwards of 4,000), the page eventually throws a 'Page Unavailable' error. After one or two tries, the scheme will successfully be associated with the Project / Issues, but the error can confuse the user and make it seem as though it did not complete.

Environment

Not Applicable, only been tested on Cloud

Steps to Reproduce

1. Step 1 - Choose the specific project you need to associate a security scheme with (a project with thousands of issues), and select Issue Security in Project Administration.
2. Step 2 - Attempt to associate a security scheme with the project and all contained issues. After step 2, the error will likely be thrown.

Expected Results

The security scheme is associated without any issues.

Actual Results

The scheme often associates, but the error is thrown. Also, when this occurs, I've seen the following Warning in the JIRA log file that I believe is related:

2015-05-19 12:12:02,801 TP-Processor30 WARN sysadmin 732x1125677x3 g5cybo 216.13.177.90,165.254.226.146 /secure/project/SelectProjectSecuritySchemeStep2.jspa [com.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'com.atlassian.cache.CacheException - com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1'.

Workaround

While the scheme is often associated with the first or second try, there is no workaround to avoid the 'Page Unavailable' error.