JCMA migration fails with Media Server Exception
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
JCMA migration fails with the following message in the atlassian-jira.log file:
"com.atlassian.jira.issue.attachment.AttachmentReadException: com.atlassian.jira.migration.mediaclient.MediaServerErrorException: failed to send a request to Media."
1
2
3
4
5
Caused by: com.atlassian.jira.migration.httpclient.exceptions.HttpCommunicationException: An error occurred when requesting against resource https://api.media.atlassian.com/chunk/b8cfe0b932dd50e8c9bad76cf116b6286e74cd87-102400: Received fatal alert: record_overflow
at com.atlassian.jira.migration.httpclient.exceptions.ExceptionsKt.communicationError(Exceptions.kt:13)
at com.atlassian.jira.migration.httpclient.AbstractPluginHttpClient.execute(AbstractPluginHttpClient.kt:76)
at com.atlassian.jira.migration.mediaclient.MediaClient.execute(MediaClient.kt:187)
... 10 moreDiagnosis
Environment
Server/Datacenter
Cause
The error will usually occur if the JDK on your server installation is less than 11.0.5. This is highlighted on https://stackoverflow.com/questions/54119613/sslhandshakeexception-received-fatal-alert-record-overflow/56211107#56211107
Solution
Workaround
As mentioned in the link, you can disable TLSv1.3 by specifying the same in the setenv.bat/sentenv.sh:
1
-Djdk.tls.client.protocols="TLSv1,TLSv1.1,TLSv1.2"Resolution
The long term resolution is to upgrade the JDK version on the server to 11.0.5 or greater.
Was this helpful?