DCM4CHEE behavior receiving duplicate instances

[Pablo]

When DCM4CHEE receives on study already stored, I've seen in the log that after the DICOM associations the following:

M-WRITE file:/var/lib/dcm4chee/server/default/archive2/2013/6/1/1/4BC0D8DD/5EFC3A67/C5933BE9

Finished compression 3.9742875 : 1 in 32ms

Received Instance [uid=1.2.840.113619.2.55.3.2831160836.42.1298014115.326.669] already exists - ignored

M-DELETE file:/var/lib/dcm4chee/server/default/archive2/2013/6/1/1/4BC0D8DD/5EFC3A67/C5933BE9

It would't be better to compress the file after the successfully DB instance insertion? To avoid unnecessary compression.

Why don't write the file  after the successfully DB instance  insertion? To avoid write and delete the already stored file.

Perhaps I haven't understood properly the log info. Any comments?

[Arnold Maderthaner]

the m-delete is because you have already an instance with the same sop instance uid.