Asset synchronization failure in Adobe Experience Manager (AEM) Dynamic Media
When the synchronization process fails when attempting to upload video assets larger than 2GB to AEM Dynamic Media, ensure that all necessary MIME types are included, confirm there are no firewall restrictions and verify network paths, examine any custom code or configurations that might override default client libraries or interfere with asset synchronization processes, and check to make sure videos aren’t longer than 30 minutes.
Description
Environment
Adobe Experience Manager 6.5.20 and above (AEM 6.5.20 and above) Dynamic Media/Scene7 - Stage and Development environments
Issue
When attempting to upload video assets larger than 2GB to the AEM Dynamic Media environment, the synchronization process fails. This can occur across multiple instances including development and staging environments. The failure occurs despite having previously configured settings for handling large files.
Symptoms can include:
- Video uploads not triggering or completing successfully.
- Error messages indicating a NumberFormatException during processing.
- Missing entries for certain MIME types such as application/pdf and application/postscript in configuration settings.
The problem persists even after ensuring that general settings are updated according to documentation guidelines.
Resolution
To resolve this issue, use these methods:
-
Ensure that all necessary MIME types are included in your OSGI configurations under
com.day.cq.dam.scene7.impl.Scene7AssetMimeTypeServiceImpl.config. Specifically, add missing entries for application/pdf and application/postscript.This should result in the UI option - hammer
>Assets>Dynamic Media General Setting to load and save its settings again. If individual mimetypes shouldn’t be synced to DMS7, then uncheck the enabled flag under each mimetype in/conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes. -
Confirm there are no firewall restrictions preventing access from DMS7 backoffice servers to cloud storage locations, like Amazon S3, where assets reside.
-
Verify network paths allow direct fetching of large assets by DMS7 from cloud storage.
-
Examine any custom code or configurations that might override default client libraries (
clientlibs) or interfere with asset synchronization processes. -
Videos up to 30 minutes in length are supported for DM processing. If a video has a longer duration, it might fail as a result of the longer processing time.
By using these methods, you should be able to restore functionality for uploading large video files (> 2GB) into the AEM Dynamic Media environment effectively without encountering further sync issues across different instances of your setup.