Docker with dcm4chee-arc-light-5.24.0 failed DICOM object upload in archive UI

[Jonathan Brooks]

Dear All,

Finally got somewhere with docker, I can log into the secure archive.

I was able to load data into the DCM4CHEE archive using:

docker run --rm --network=dcm4chee_default dcm4che/dcm4che-tools storescu -cDCM4CHEE@arc:11112 /opt/dcm4che/etc/testdata/dicom

which appears in the correct location after changing the storage URI and mapping the drive to the docker container (-v /something/somewhere:/storage/fs1)

However, I wanted to try uploading data through "More functions" -> "Upload DICOM object" menu from the main Navigation page:

I select the STOW-RS server = DCM4CHEE (?) pick a few dcm files, and get:

Error 500 Internal Server Error.

See attached image and server.log.

Any ideas?

Best, Jon

[Jonathan Brooks]

I had a look at the release notes for dcm4chee-arc-light-5.24.0:

....

UI Navigation - Study : Enable uploading DICOM files only for web applications consisting STOW_RS web service class #3281

....

It seems like one can no longer upload from the UI? Or have I misread this?

I was able to upload using storescu, but I wanted to check if I've missed something in the configuration that's stopping me uploading.

Either way it's not a big thing - just slightly weird that it's not working in the containerized version....?

Best wishes,

Jon

[Jonathan Brooks]

Should add that even if I select the STOW-RS server as stowrsd it still won't upload.

Images attached (really) this time,.

Cheers, Jon

[Vrinda Nayak]

https://github.com/dcm4che/dcm4chee-arc-light/issues/3281 was only about showing a filtered list of web applications containing STOW_RS as a Web Service Class in its configuration.

For Internal Server Errors on uploading using DCM4CHEE web application, please check the server.log. For uploading to stowrsd, ensure you have started the tool.

[Jonathan Brooks]

Hi Vrinda,

Thanks, so I'm just using the vanilla docker container installation - I don't know if that starts stowrsd by default? How would I check? If I select DCM4CHEE should that work? The reason I ask is because this (selecting STOW-RS -> DCM4CHEE, upload DICOM) works perfectly with an install of dcm4chee-arc-light-5.23.3 (not secured, not docker), so I was wondering if it should work on a docker (secured) install?

Please see attached wildfly-server.log from attempt to upload single DICOM image to secured docker install, I've also included keycloak-server.log

Not sure if there's anything helpful in there?

Cheers, Jon

[Vrinda Nayak]

The DICOM file you tried to upload seems corrupted.

2021-08-11 11:47:09,850 INFO  [org.dcm4chee.arc.stow.StowRS] (default task-6) Process POST /dcm4chee-arc/aets/DCM4CHEE/rs/studies from b0dd0f86-0f23-4a8b...@192.168.0.76
2021-08-11 11:47:09,860 INFO  [org.dcm4chee.arc.stow.StowRS] (default task-6) storeInstances: Extract Part #1{content-disposition=[form-data;name="file";filename="MR000000.dcm"], content-type=[application/dicom]}
2021-08-11 11:47:09,905 WARN  [org.dcm4che3.io.DicomInputStream] (default task-6) IOException during read of (0000,0000) #1128875008 @ 123: java.io.EOFException
    at org.dcm4...@5.24.0//org.dcm4che3.util.StreamUtils.readFully(StreamUtils.java:74)

Try upload function with a valid DICOM file.

[Jonathan Brooks]

Hi Vrinda,

I think the files are okay....

storescu -c DCM4CHEE@ubicdicom:11112 /home/dicom/Downloads/studyID/protocol/MR_t1_qfl3d_sag_p2_iso1mm/MR*dcm

Uploaded all 192 DICOM files from the same folder without error. I was able to browse them in the archive and download without issue.

Not sure why they would appear as corrupt when trying to upload the exact same files via the UI.

Best wishes,

Jon

[Jonathan Brooks]

Not sure if this helps identify the problem, but here are the relevant parts of firefox inspector:

Best,

Jon

[Michael Bowen]

Was a solution ever found? I had the same issue, unable to upload running into an EOF Exception.