S3 Upload Failure: dcm4chee Writes DB Entry Even When PUT Fails

[Andreiver Mateus]

I'm facing an issue when dcm4chee tries to store objects in an S3 backend (MinIO).
Sometimes the upload of some images fails with the following exception:

ERROR [org.jclouds.http.handlers.BackoffLimitedRetryHandler] (EE-ManagedExecutorService-default-Thread-271971) Cannot retry after server error, command is not replayable:
[method=org.jclouds.s3.S3Client.putObject(...),
request=PUT http://IP:PORT/bucket/EF7756D4/2025/12/10/C5DAD091/5CFBB420/7FBE6118 HTTP/1.1]

This does not happen for the whole study, only for a few images.

The problem is that even when the PUT request fails, dcm4chee still writes the storage path to the database, as if the object was successfully stored.
So the entry exists in the DB, but the file does not exist in the S3 bucket.

This results in inconsistent storage and broken studies.

Is this a known issue?
Should dcm4chee validate the PUT response before persisting the object location in the database?

Any guidance would be greatly appreciated.

Thanks.

[Andreiver Mateus]

dcm4chee-arc version is 5.34.0