Pending Replication Queue | Community
Skip to main content
V
Vignesh_K_S
Level 2
June 16, 2025
Solved

Pending Replication Queue

  • June 16, 2025
  • 5 replies
  • 652 views

I'm working with AEM 6.5 version. whenever I publish the sites or assets it is getting queued even after clearing it still same issue. 

checked the publisher connection, test connection got succeeded. so, this is not related to connection issue

In error log file getting the below error messages
Error while sending request: java.io.IOException: java.io.IOException: org.apache.jackrabbit.core.data.DataStoreException: Record 561150a7cgf9a1aef2eb66e5d74248756044bfdd67712da3c804a2a8877f542d does not exist
ERROR - publish1 : Replication (ACTIVATE) of /content/dam/test.jpg not successful: java.io.IOException: java.io.IOException: org.apache.jackrabbit.core.data.DataStoreException: Record 561150a7cgf9a1aef2eb66e5d74248756044bfdd67712da3c804a2a8877f542d does not exist Conversation follows

Please help to resolve the issue.
Thanks!

    Best answer by rahulp76079001

    Hi @vignesh_k_s ,

     

    As per the log snippet provided by you, it seems the mentioned datastore segment is missing, you need to check if you are having enough space in you AEm instance. then restore the correct segment store and start your AEM. it should start working properly.

     

    Thanks

    5 replies

    SantoshSai
    Community Advisor
    SantoshSaiCommunity Advisor
    Community Advisor
    June 16, 2025

    Hi @vignesh_k_s,

    I came across similar issue earlier - involving corrupt or missing binaries in the DataStore, and it directly causes replication queue blocks with such errors

    You're using a FileDataStore or S3DataStore in AEM, and the error means:

    The referenced binary record (561150a7cgf9...) is missing or corrupted in the datastore. This breaks replication because the asset cannot be read and transferred.


    1. Run DataStore consistency check

    Please google some steps how to confirm which binaries are missing according to your setup.

    2. Re-ingest or Re-upload missing assets

    Once you find the asset(s) causing the issue:

    • Try to re-upload or re-ingest the asset (/content/dam/test.jpg) from source.

    • If the original file is unavailable, consider removing the broken node from the repository:
      /content/dam/test.jpg /jcr:content/metadata /jcr:content/renditions/original

      Caution: Make sure you’re deleting only if re-upload isn’t an option.

    3. Clear replication queue

    After the problematic asset is removed or replaced:

    Santosh Sai
      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      June 17, 2025

      Hi @vignesh_k_s 

      Please check the error log, some of segments might be corrupted.

      Arun Patidar
        rahulp76079001
        rahulp76079001Accepted solution
        Level 2
        June 17, 2025

        Hi @vignesh_k_s ,

         

        As per the log snippet provided by you, it seems the mentioned datastore segment is missing, you need to check if you are having enough space in you AEm instance. then restore the correct segment store and start your AEM. it should start working properly.

         

        Thanks

          ButhpurKiran
          ButhpurKiran
          Level 4
          June 18, 2025

          Hi,

           

          Check that both author and publish instances are either using the same shared DataStore or, if using local DataStores, that replication is correctly pushing binaries; review the sling.properties and repository.xml files for proper DataStore settings. Next, on the publish instance, verify the DataStore folder (usually /crx-quickstart/segmentstore/datastore) exists and contains the necessary files, ensuring correct file permissions so AEM can access them. Run DataStore garbage collection to clean up any orphaned blobs and fix inconsistencies, which can be done through the Web Console or commands. If you use a shared DataStore, try resyncing the files between author and publish, or rebuild the DataStore if corrupted. Also, confirm the replication agent on author is set to push binaries and that the transport user has the right permissions to access content and binaries. Now, review logs for any errors related to Blob Garbage Collection or DataStore consistency to identify further issues.

          Kind regards,

          Kiran Buthpur

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            June 23, 2025

            @vignesh_k_s Did you find the suggestions helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you.

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...