Details
-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
None
-
None
-
68
-
Minor
Description
Issue Summary
When doing a Jira site import, the import may fail during the user processing phase, the error message is not clear in the UI. However, the stack error indicates there is a throttling happening in the backend or socketTimouts, usually, this specific problem happens with large user bases.
Steps to Reproduce
- Create a backup
- Perform a site import
Expected Results
Import completes successfully
Actual Results
Import fails with the following generic message in the UI:
Note: This is a generic error message to confirm the real issue, support needs to investigate the backend logs.
The exception can be seen in the backend logs. Note that there seem to be multiple manifestations of the same issue through different errors.
com.atlassian.idp.client.exceptions.ThrottledException: { "error" : "Too many requests. Please inspect Retry-After header." }
com.atlassian.idp.client.IdentityPlatformClientImpl.mapStatusCodeException(IdentityPlatformClientImpl.java:519)
com.atlassian.idp.client.IdentityPlatformClientImpl.mapInputStream(IdentityPlatformClientImpl.java:461)
com.atlassian.idp.client.IdentityPlatformClientImpl.makeRequestWithEntityBody(IdentityPlatformClientImpl.java:435)
com.atlassian.idp.client.IdentityPlatformClientImpl.createGroup(IdentityPlatformClientImpl.java:313)
com.atlassian.crowd.exception.runtime.OperationFailedException: javax.net.ssl.SSLException: Socket closed at com.atlassian.jira.bc.dataimport.identity.DefaultIdpSafeOperations.withRetry(DefaultIdpSafeOperations.java:313) at com.atlassian.jira.bc.dataimport.identity.DefaultIdpSafeOperations.importUserReturningExisting(DefaultIdpSafeOperations.java:233) at com.atlassian.jira.bc.dataimport.identity.UsersOperations.lambda$createNewUserWithGroupMemberships$20(UsersOperations.java:483) at com.atlassian.jira.util.retry.Retryer$Retriable.call(Retryer.java:94)
Workaround
Front-load the users using a script, contact support strip the users from the entities.xml.
