-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DICOM upload via the UI fails if more than 20 files are selected #13
Comments
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? |
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. |
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! |
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.... |
Same issue on my machine, but the issue only appears if files are more than 16 |
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.
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
The text was updated successfully, but these errors were encountered: