Expand my Community achievements bar.

Migrating to the AEM Cloud using Content Transfer tool and experiencing a Length Collision that is stopping the Extraction


Level 1

Hi all --


I am working on a AEMaaCS migration using the Content Transfer Tool and we are experiencing an Exception during Extraction phase that is causing it to fail. 

The exception is org.apache.jackrabbit.core.data.DataStoreException: Length Collision (see below) and the source is an AEM 6.5 SP13 instance w/ content-transfer.all-3.0.0.zip package installed.  


The extraction configuration includes a wipe "Overwrite staging container during extraction" and include versions is part of the Migration Set configuration. Pre copy and User mapping is not part of the Migration Set configuration. 

Any thoughts on how to resolve?  I am running a consistency check now -- but that is generally to identify missing binaries.  I am at a loss on this issue since it seems related to the Azure Blob Store being targeted. 




2023-09-10 12:28:09,672 [oak-ds-async-upload-thread-9] ERROR o.a.j.o.p.blob.UploadStagingCache - Error adding file to backend
org.apache.jackrabbit.core.data.DataStoreException: Length Collision. identifier=9dfc-c60cca9f3902f323f080762930328e64b704b2fa1b7a8c25df6f68dabc7d new length=0 old length=5770
	at org.apache.jackrabbit.oak.blob.cloud.azure.blobstorage.AzureBlobStoreBackend.write(AzureBlobStoreBackend.java:312)
	at org.apache.jackrabbit.oak.plugins.blob.AbstractSharedCachingDataStore$2.write(AbstractSharedCachingDataStore.java:173)
	at org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache$3.call(UploadStagingCache.java:367)
	at org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache$3.call(UploadStagingCache.java:362)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)





0 Replies