DCM4CHEE 5.22 DICOM listener hangs

[Antoni Regeling]

Hi,

I've just installed DCM4CHEE arc light version 5.22.1 on RHEL 8 and while most everything appears to be working fine and the archive doesn't log any errors I'm running into a strange problem with it accepting incoming DICOM associations.

When I have an SCU try and connect to it (e.g. to a DICOM echo), the archive will accept the incoming connection at the socket level but then it just sits there and nothing happens and the SCU will at some point time out and give up and report that the C-ECHO failed because there was no response from the DCM4CHEE archive.

The weird thing is that when I stop the archive - it then proceeds to accept the incoming association request, but then of course it logs an error due to a broken pipe - the other end has disconnected.

If I stop the archive before the SCU times out, then the association request is actually accepted and the C-ECHO actually succeeds. Below is what DCM4CHEE logged when I did that.

At 8:35:55 the SCU tries to initiate an association and DCM4CHEE accepts the connection at the socket level:

08:35:55,617 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.17.50.11,port=49346,localport=11112]

Then it just sits there for some 9 seconds before me hitting the 'stop archive button' - and then it proceeds processing the association request as shown below:

08:36:04,886 INFO  [org.dcm4chee.arc.ctrl.ArchiveCtrl] (default task-12) Process POST /dcm4chee-arc/ctrl/stop from nu...@10.17.50.11

08:36:04,892 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) >> A-ASSOCIATE-RQ

08:36:04,893 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) << A-ASSOCIATE-AC

08:36:04,894 INFO  [org.dcm4chee.arc.delete.impl.PurgeStorageScheduler] (EE-ManagedExecutorService-default-Thread-3) Finished deletion on Storage[id=fs1, uri=file:/opt/wildfly/standalone/data/fs1/]

08:36:04,909 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) >> 2:C-ECHO-RQ[pcid=1

  cuid=1.2.840.10008.1.1 - Verification SOP Class

  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]

08:36:04,911 INFO  [org.dcm4chee.arc.ctrl.ArchiveCtrl] (default task-12) Process GET /dcm4chee-arc/ctrl/status from nu...@10.17.50.11

08:36:04,913 INFO  [org.dcm4che3.net.Dimse] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) << 2:C-ECHO-RSP[pcid=1, status=0H

  cuid=1.2.840.10008.1.1 - Verification SOP Class

  tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]

08:36:13,765 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) >> A-RELEASE-RQ

08:36:13,765 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-1) DCM4CHEE<-TONSTEST(7) << A-RELEASE-RP

08:36:13,817 INFO  [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-4) DCM4CHEE<-TONSTEST(7): close Socket[addr=/10.17.50.11,port=49346,localport=11112]

Does anyone have any idea as to what the problem might be?

Thanks

Ton Regeling

[Antoni Regeling]

Found the issue, Increasing the max number of threads solved it.

Ton