Issue indexing is very slow when JIRA Agile 6.4.3 or higher is installed on Oracle database

Symptoms

When JIRA Agile 6.4.3 is installed on JIRA < 6.3.7, indexing of issues takes an extremely long time. Any edit operation on an issue will take between 5-10 seconds per LexoRank custom field that exists in the system. This happens only when using an Oracle database.

Steps to Reproduce

1. Install JIRA 6.0 or 6.1
2. Install JIRA Agile 6.4.3
3. Edit an issue and notice that it takes up to 10 seconds to save
4. Run a full reindex and notice that it takes an exceptionally long time. For example if it normally took about a minute to do a full reindex, it might take up to two hours

Diagnosis

1. Run the profiling, as in enabling profiling documentation
2. Create a JIRA issue to reproduce the problem
3. Disable profiling log to prevent spamming application log file
4. In the atlassian-jira.log, you should see something like the following

   2014-09-01 20:29:05,992 http-bio-2969-exec-5 DEBUG jiraadmin 1228x9018x1 3t9mem 172.22.236.xxx /secure/QuickCreateIssue.jspa [atlassian.util.profiling.UtilTimerStack] [21376ms] - /ghs-12926/secure/QuickCreateIssue.jspa
     [0ms] - PermissionManager.hasPermission()
     [21373ms] - QuickCreateIssue.execute()
       [28ms] - PermissionManager.getProjects()
       [0ms] - List.contains()
       .....
       [17057ms] - IssueIndexManager.reIndexIssueObjects()
       .....
   

   See the IssueIndexManager.reIndexIssueObjects() spiking to 17s

Notes

This is caused by a bug in Active Objects tracked in AO-549 - note that this issue only affects the Oracle database.