search

dcm4che-dockerfiles / dcm4chee-arc-psql

35 stars 50 forks source link

DICOM upload via the UI fails if more than 20 files are selected #13

Open Christian-e-S opened 3 years ago

Christian-e-S commented 3 years ago

Dear All,

The DICOM upload function via the UI works very well if I select only a small number of files (e.g., 10 files).

When I select more than 20 files, the status bars of all the uploads get stuck, and the server logs show a "java.nio.channels.ClosedChannelException" for each of the uploads.

image

Could it be, that a there are too many concurrent data base operations?

I have included the stack trace

stack_trace_ClosedChannelException.txt

Used Image: dcm4che/dcm4chee-arc-psql:5.23.1-secure

Christian-e-S commented 3 years ago

I have verified that this issue exists also in dcm4che/dcm4chee-arc-psql:5.23.2-secure.

Would it be a solution to restrict the UI that it calls the POST request only for a limited set of images at a time? What I mean is when the user selects 300 images to upload, the UI would first upload the first set of 10 images, after completion the next set of 10, ... and so on. That would minimize the number of required open connections.

What do you think?

gunterze commented 3 years ago

You may try to increase the number of available threads by ENV WILDFLY_EXECUTER_MAX_THREADS.

There is an open issue to Upload multiple DICOM/Bulkdata Objects in one STOW-RS request which would significantly reduce the server load.

Christian-e-S commented 3 years ago

Increasing ENV WILDFLY_EXECUTER_MAX_THREADS did not resolve the issue, but Upload multiple DICOM/Bulkdata Objects in one STOW-RS request sounds like an excellent approach.

Thanks!

gunterze commented 3 years ago

Optimally, the UI shall support both: packing multiple objects in one request and limiting the maximal number of concurrent requests to a configurable number.

Will also investigate, what actually causes the failure on server side....

shral commented 2 years ago

I just tested on my side, I could upload 47 files without problem, but anyway I could work on limiting the maximal active services at once. Sending all DICOM files in one request will remove the feature of showing the load process for each file the question is if we really want that. image

jason1122g commented 2 years ago

Same issue on my machine, but the issue only appears if files are more than 16
This issue might be irrelevant with file size, I have tried files <= 16 with larger total size and the issue does not appear I have also tried to increase WILDFLY_EXECUTER_MAX_THREADS but not working :thinking: