Unable to fetch Jira issues' details using Jira macro after upgrade to 6.14.1

[willa]

Few days ago, our home hosted confluence v6.6.12 was experiencing high CPU utilization. We successfully upgraded to v6.14.1. Unfortunately, immediately after the upgrade Jira macro was not able to pull issues details. The strange thing is when searching for issues, it works just fine (I know this because it displays the list of all possible matches and I can select from it).

The problem is when loading the page, the system fails to fetch associated issue details. Below is what happens.

First, this happens for a while. (Obviously showing that the system is trying to fetch information from Jira)

Then, it fails showing this.

Looking in the `atlassian-confluence.log` file does not show anything significant, or at least I don't see anything related to failure in loading information from Jira except for some few WARNINGs (not errors) related to XSRF checkup failure. Before I forget, both Jira & Confluence run in tomcat servers deployed using docker behind an nginx reverse proxy instance also deployed using docker. I have configured the server.xml of both services' tomcat servers with proxy settings specifying their expected domain names.

Here is a portion of the logs that appear repeatedly when attempting to load the page.

2019-04-22 17:03:50,773 WARN [http-nio-8090-exec-2] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 109 in HQL: [from com.atlassian.confluence.internal.relations.dao.User2ContentRelationEntity
re where re.targetContent = ? and re.relationName = ?]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
-- referer: https://wiki.domain.org/pages/editpage.action?pageId=26116106 | url: /rest/api/content/26116106 | traceId: 6945de4e594e2a54 | userName: user129900
2019-04-22 17:03:50,775 WARN [http-nio-8090-exec-2] [hql.internal.ast.HqlSqlWalker] generatePositionalParameter [DEPRECATION] Encountered positional parameter near line 1, column 133 in HQL: [from com.atlassian.confluence.internal.relations.dao.User2ContentRelationEntity
re where re.targetContent = ? and re.relationName = ?]. Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
-- referer: https://wiki.domain.org/pages/editpage.action?pageId=26116106 | url: /rest/api/content/26116106 | traceId: 6945de4e594e2a54 | userName: user129900
2019-04-22 17:04:27,665 INFO [Caesium-1-1] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation for directory [ 753665 ] starting
2019-04-22 17:04:27,667 INFO [Caesium-1-1] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache Attempting INCREMENTAL synchronisation for directory [ 753665 ]
2019-04-22 17:04:27,939 INFO [Caesium-1-1] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache INCREMENTAL synchronisation complete for directory [ 753665 ] in [ 274ms ]
2019-04-22 17:04:28,330 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is tu
rned off']
2019-04-22 17:06:10,811 WARN [http-nio-8090-exec-4] [common.security.jersey.XsrfResourceFilter] passesAdditionalBrowserChecks Additional XSRF checks failed for request: https://wiki.domain.org/rest/tinymce/1/macro/preview , origin: null , referrer: https://<ip address omitted here>
:443/pages/resumedraft.action , credentials in request: false , allowed via CORS: false
-- referer: https://<ip address omitted here>:443/pages/resumedraft.action?draftId=21162&draftShareId=6ed4bb1b-bddb-42b6-bf04-7305e9f03640& | url: /rest/tinymce/1/macro/preview | traceId: 81a08b4a1b125969 | userName: anonymous
2019-04-22 17:09:28,332 WARN [Caesium-1-3] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is tu
rned off']
2019-04-22 17:11:31,458 WARN [http-nio-8090-exec-1] [common.security.jersey.XsrfResourceFilter] passesAdditionalBrowserChecks Additional XSRF checks failed for request: https://wiki.domain.org/rest/tinymce/1/macro/preview , origin: null , referrer: https://<ip address omitted here>
:443/pages/resumedraft.action , credentials in request: false , allowed via CORS: false
-- referer: https://<ip address omitted here>:443/pages/resumedraft.action?draftId=15628&draftShareId=e4b4565c-c555-4085-8d2f-b2fa94c1bcb5& | url: /rest/tinymce/1/macro/preview | traceId: 84a547a9f3ecaeb0 | userName: anonymous
2019-04-22 17:11:32,858 WARN [http-nio-8090-exec-2] [common.security.jersey.XsrfResourceFilter] passesAdditionalBrowserChecks Additional XSRF checks failed for request: https://wiki.domain.org/rest/tinymce/1/macro/preview , origin: null , referrer: https://<ip address omitted here>
:443/pages/resumedraft.action , credentials in request: false , allowed via CORS: false
-- referer: https://<ip address omitted here>:443/pages/resumedraft.action?draftId=26661&draftShareId=e91d04f4-d820-4e9e-b8d0-203c55f943b0& | url: /rest/tinymce/1/macro/preview | traceId: ca837104b006483e | userName: anonymous
2019-04-22 17:12:40,112 WARN [http-nio-8090-exec-9] [common.security.jersey.XsrfResourceFilter] passesAdditionalBrowserChecks Additional XSRF checks failed for request: https://wiki.domain.org/rest/tinymce/1/macro/preview , origin: null , referrer: https://<ip address omitted here>
:443/pages/resumedraft.action , credentials in request: false , allowed via CORS: false
-- referer: https://<ip address omitted here>:443/pages/resumedraft.action?draftId=17837&draftShareId=a002e0f9-d4c2-40af-a099-7aeb80e17e1c& | url: /rest/tinymce/1/macro/preview | traceId: 5ee2204ac7fd8011 | userName: anonymous
2019-04-22 17:14:28,331 WARN [Caesium-1-2] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is tu
rned off']
2019-04-22 17:19:28,330 WARN [Caesium-1-1] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job LaasPerformanceLoggingJob#LaasPerformanceLoggingJob completed unsuccessfully with response JobRunnerResponse[runOutcome=ABORTED,message='LaaS performance logging is tu
rned off']
2019-04-22 17:24:19,756 WARN [http-nio-8090-exec-4] [apache.commons.httpclient.SimpleHttpConnectionManager] getConnectionWithTimeout SimpleHttpConnectionManager being used incorrectly. Be sure that HttpMethod.releaseConnection() is always called and that only one thread
and/or method is using this connection manager at a time.

To recap, here is what we have so far.

1. Upgraded Confluence from 6.6.12 to 7.14.1
2. Upgraded Jira from 7.3.1 to 7.13.1 (because 7.3.1 is end of life)
3. Upgraded all plugins on both Confluence & Jira.
4. Removed and recreated the application links. 
5. Both seem to work perfectly fine independently.
6. I can use Jira macro on Confluence to pull tickets but not associated details).

So, the question is what is happening? Why is Confluence not able to pull the associated Jira issues' details? What can I do to resolve this?

Any help is highly appreciated.

[willa]

Since I haven't received any solution so far I decided to debug this. Unfortunately, I could not compile the confluence jira plugin because of some unsatisfied atlassian closed source dependencies! At this point you can imagine my frustration. Anyway I used the chrome dev tools to examine the javascript making the ajax request. These are the lines of code handling this request on the backend, as it turns out this piece of code for some reason I have yet to understand keep returning HTTP 202, even after multiple retries from the client! 

Following this line led me to a wall because the class/interface com.atlassian.vcache.JvmCache is apparently closed source as well. I also discovered that, I am able to view the list of issues when searching because the request is handled by a different servlet.

At this point, I don't know what else to do. Is Atlassian reading these posts at all?

[JP _AC Bielefeld Leader_]

What database are you using? The first lines of the log point to a DB issue.

[willa]

MySQL