DCM4CHEE deletes instance file when the same instance UID is received twice in a row

[pitz-signalpet]

Describe the bug

It seems that when the same instance UID is sent twice in succession, triggering a replacement, it's possible for DCM4CHEE to delete both the previous and the new instance.

Following the logs below, DCM4CHEE is no longer able to access the instance because the file does not exist.

My guess is that since both old and new instances got the same storage path, when DCM4CHEE tried to delete the old instance it actually deleted the new one. I'm not sure how it was possible for both instances to get the same storage path.

Additional context

• The storage is an AWS S3 bucket.
• Using DCM4CHEE 5.33.1.
• dcmOverwritePolicy=SAME_SOURCE (default)

Logs

2025-07-02 20:51:41,690 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744): Found previous received Instance[pk=1675962, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,690 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744): Replace previous received Instance[pk=1675962, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,708 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744): Create Instance[pk=1677829, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,709 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744): Create Location[pk=1677829, systemID=main, path=prod/2025/07/02/2C3A0DAB/F04A39B9/2F86E1F6, tsuid=1.2.840.10008.1.2.4.90, size=3048114, status=OK, objectType=DICOM_FILE]
2025-07-02 20:51:41,718 INFO [org.dcm4chee.arc.store.impl.StoreServiceImpl] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744): Updated DB in 38 ms
2025-07-02 20:51:41,725 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744) << 1:C-STORE-RSP[pcid=7, status=0H
2025-07-02 20:51:41,727 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744) >> A-RELEASE-RQ
2025-07-02 20:51:41,727 INFO [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-2494) DCM4CHEE<-STORESCU(5744) << A-RELEASE-RP
2025-07-02 20:51:41,777 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-6) DCM4CHEE<-STORESCU(5744): close Socket[addr=***,port=35211,localport=11112]
2025-07-02 20:51:41,896 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745): Found previous received Instance[pk=1677829, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,896 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745): Replace previous received Instance[pk=1677829, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,907 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745): Create Instance[pk=1677830, uid=1.2.840.1136982025070203262189666.4, class=1.2.840.10008.5.1.4.1.1.1.1, no=1]
2025-07-02 20:51:41,908 INFO [org.dcm4chee.arc.store.impl.StoreServiceEJB] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745): Create Location[pk=1677830, systemID=main, path=prod/2025/07/02/2C3A0DAB/F04A39B9/2F86E1F6, tsuid=1.2.840.10008.1.2.1, size=4512184, status=OK, objectType=DICOM_FILE]
2025-07-02 20:51:41,916 INFO [org.dcm4chee.arc.store.impl.StoreServiceImpl] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745): Updated DB in 27 ms
2025-07-02 20:51:41,921 INFO [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-2496) DCM4CHEE<-STORESCU(5745) << 1:C-STORE-RSP[pcid=5, status=0H

[andreiSeer]

The same issue occurred in my environment. Fortunately, we use S3 with versioning enabled. We are on version 5.28 and have dcmOverwritePolicy=No.