-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Space - Content Manager
-
2
-
Minor
Issue Summary
Confluence space Content Manager provides the ability for admins to perform bulk actions on pages in a space.
When you select the parent page then all descendants of the parent is automatically selected in Content Manager.
If there are 1000+ descendant pages then the Content Manager crashes and displays
"Something went wrong. Try again in few minutes"
This is reproducible on Data Center: NA
Steps to Reproduce
- Go to a space
- Create a parent page
- Now create over 1000 (1000-1200) child pages under the parent page, using REST API or automation.
- Go to Space Content Manager
- select the checkbox next to parent page to select all child pages.
Expected Results
All child pages should be selected and at the bottom of the page the bulk actions menu will display total number of pages.
Actual Results
Error is shown
In DevTools we can see following graphQL API fails.
https://wiki.confluence.dvindika.com/cgraphql?q=PostselectionAdditionalDataQuery
endpoint returns HTTP 200 OK but with below result
[
{
"errors": [
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"pageContent"
],
"extensions": {
"classification": "DataFetchingException"
}
},
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"databaseContent"
],
"extensions": {
"classification": "DataFetchingException"
}
},
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"whiteboardContent"
],
"extensions": {
"classification": "DataFetchingException"
}
},
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"blogpostContent"
],
"extensions": {
"classification": "DataFetchingException"
}
},
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"embedContent"
],
"extensions": {
"classification": "DataFetchingException"
}
},
{
"message": "Exception querying the remote GraphQL service: java.net.SocketTimeoutException: 10,000 milliseconds timeout on connection http-outgoing-286754 [ACTIVE]",
"locations": [],
"path": [
"folderContent"
],
"extensions": {
"classification": "DataFetchingException"
}
}
],
"data": {
"pageContent": null,
"databaseContent": null,
"whiteboardContent": null,
"blogpostContent": null,
"embedContent": null,
"folderContent": null
}
}
]
It looks like if the API does not process within 10,000 milliseconds (10 seconds), the socket is set to time out.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available