Creating multiple issues from a table will throw a parse error if the table has a lot of data

Summary

Using the Product Requirements template, if you populate the Requirements table with a lot of data on each cell and the table has many lines (more than 60), when you try to create multiple Jira issues from this Requirements table the operation will not complete, it will just create a few issues and a parse error will be presented on the top of the page:

Steps to Reproduce

1. Create a page using the Product Requirements template
2. Populate the Requirements table (both Title and User Story columns) with a lot of data (at least 160 characters on each cell on the Title column and at least 290 characters in the Story column)
3. Make the Requirements table with at least 60 lines following the requirements above for each line
4. Go to the first line and try to create multiple Jira issues from this Requirements table

Expected Results

All issues are created on Jira and linked back to Confluence.

Actual Results

A parse error will be presented on the top of the page:

Also we can see a 500 error on the browser's console on the POST to the jira-integration REST:

POST https://<instance>.atlassian.net/wiki/rest/jira-integration/1.0/issues?applicationId=5c4edae1-bbd1-36a8-b45a-e54a072fbfee 500 () VM1606 jquery-min.js:3
send	@	jquery-min.js:3
ajax	@	jquery-min.js:3
createIssues	@	VM1937 com.atlassian…t__&locale=en-GB:25
_executeCreateJiraIssue	@	VM1940 com.atlassian…__&locale=en-GB:299
createIssues	@	VM1940 com.atlassian…__&locale=en-GB:299
submitFormWhenValid	@	VM1940 com.atlassian…__&locale=en-GB:289
a.startValidation	@	VM1940 com.atlassian…__&locale=en-GB:274
submit	@	VM1940 com.atlassian…__&locale=en-GB:284
_onSubmitForm	@	VM1940 com.atlassian…__&locale=en-GB:299
dispatch	@	jquery-min.js:2
s	@	jquery-min.js:2

Also the following warning appears on the Confluence log:

2017-09-13T18:07:59.526Z
WARN
Problem communicating with JIRA: java.net.SocketTimeoutException: Read timed out

Notes

This problem may be intermittent from tenant to tenant, so it may not happen 100% of times.

Workaround

None.