DCM4CHEE stops processing requests

Niels Wahlgreen

unread,

Nov 15, 2019, 9:47:10 AM11/15/19

to dcm4che

Dear all,

We have four PACS servers running DCM4CHEE 5.18.1. We started those servers at 5.17.0 and from the beginning, they have been hanging ocassionally.

Most of the time, everything works great and fast. But sometimes, the server stops responding.

When the problem occurs:

- The webinterface still works, but very slowly

- DICOM requests fail

- Right when it happens, it continues processing the requests that were received before the event and until they are done

- If we restart WildFly everything works again - sometimes for two weeks, other times for 5 minutes.

It seems like the problems happen most, when the system is under load - very often while we are receiving or sending CT or MRI scans, since they have many more images than an ultrasound or X-ray study.

When the problem is there, requests are still coming in and being accepted, but nothing is done with them, as you can see in the logfile below.

We have tried increasing the memory for the WildFly instance and increasing threads and it doesn't seem to help.

When the problem occurs, it does not seem like anything particular is logged. We normally check the previous minutes of log file when it happens, but we haven't found anything unusual. It seems like it is operating at full speed, until it hits some kind of event/limit.

Nov  1 08:23:00 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:23:00,732 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.1.1.58,port=49709,localport=11112]
Nov  1 08:23:34 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:23:34,223 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=64898,localport=11112]
Nov  1 08:23:44 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:23:44,744 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.109,port=51871,localport=11112]
Nov  1 08:24:34 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:24:34,250 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=65008,localport=11112]
Nov  1 08:25:26 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:25:26,722 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.1.1.58,port=49717,localport=11112]
Nov  1 08:25:34 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:25:34,497 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=65113,localport=11112]
Nov  1 08:26:07 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:26:07,721 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.1.1.58,port=49724,localport=11112]
Nov  1 08:26:34 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:26:34,460 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=65226,localport=11112]
Nov  1 08:27:20 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:27:20,695 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.1.1.58,port=49738,localport=11112]
Nov  1 08:27:34 pacs_cph1 standalone.sh[18707]: #033[0m#033[0m08:27:34,304 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=65307,localport=11112]

Gunter Zeilinger

unread,

Nov 15, 2019, 9:55:49 AM11/15/19

to dcm...@googlegroups.com

https://groups.google.com/d/topic/dcm4che/F5WH8JgnDqE/discussion

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/45ba6fa5-2f44-4bb4-814d-edf76884efd3%40googlegroups.com.

Niels Wahlgreen

unread,

Nov 15, 2019, 10:33:05 AM11/15/19

to dcm4che

Hi Gunther,

Thank you. We are not using Docker, but we tried adjusting that parameter from the WildFly console today. Now we will wait to see if it helps when the doctors are back on monday.

However, we didn't get the Exception in the log file that Andor refers to, so I am not sure that it is the same error?

Niels Wahlgreen

unread,

Dec 30, 2019, 7:02:50 AM12/30/19

to dcm4che

Dear all,

We have previously written about a problem we have, when our PACS servers experience heavy load.

When we receive CT studies, often containing around 6000 images, sometimes dcm4chee stops responding on the DICOM port. Web interface still works in these cases.

We are running dcm4chee 5.20.0 (but have had the problem with all versions since 5.16 when we initially started the servers) on Ubuntu 18.04 LTS, Wildfly 17.0.1.final, not using Docker. When it happens, it still accepts connections, but does nothing after accepting the connection, as can be seen in the log below.

We have tried the following, to remedy the problem:

- Assigning a lot of RAM (currently uses 1974/7282MB assigned to Wildfly)

- Subsystem -> EE -> Executor -> Max Threads set to 1000 (this helped a lot, but we still experience daily downtime. Today, I increased it to 2.000, to see how high we can go, before we reach the OS limit on threads).

- Tuning of Ubuntu to allow more open file handles etc.

- Moved archive to SSD storage

We would really appreciate anything that could point us in a direction that can resolve this. Are there any other performance related settings that we need to be aware of?

Dec 30 11:11:31 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:11:31,826 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55542,localport=2575]

Dec 30 11:11:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:11:32,302 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-67) start ExportScheduler.execute()

Dec 30 11:11:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:11:32,303 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-67) finished ExportScheduler.execute()

Dec 30 11:11:47 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:11:47,428 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=36203,localport=11112]

Dec 30 11:12:02 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:02,481 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55554,localport=2575]

Dec 30 11:12:06 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:06,065 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.12.50.79,port=54120,localport=11112]

Dec 30 11:12:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:09,450 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1002) start IANScheduler.execute()

Dec 30 11:12:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:09,451 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1002) finished IANScheduler.execute()

Dec 30 11:12:10 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:10,552 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.110,port=51960,localport=11112]

Dec 30 11:12:12 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:12,501 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55560,localport=2575]

Dec 30 11:12:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:15,937 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-582) start AuditScheduler.execute()

Dec 30 11:12:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-582) finished AuditScheduler.execute()

Dec 30 11:12:22 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:22,502 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55566,localport=2575]

Dec 30 11:12:22 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:22,557 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=35937,localport=11112]

Dec 30 11:12:28 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:28,230 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.12.50.73,port=62968,localport=11112]

Dec 30 11:12:28 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:28,552 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=50811,localport=11112]

Dec 30 11:12:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:32,303 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-584) start ExportScheduler.execute()

Dec 30 11:12:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:32,303 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-584) finished ExportScheduler.execute()

Dec 30 11:12:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:32,518 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55570,localport=2575]

Dec 30 11:12:38 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:38,742 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.3.10,port=60434,localport=11112]

Dec 30 11:12:57 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:12:57,684 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=51973,localport=11112]

Dec 30 11:13:02 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:02,171 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55582,localport=2575]

Dec 30 11:13:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:09,451 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1733) start IANScheduler.execute()

Dec 30 11:13:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:09,452 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1733) finished IANScheduler.execute()

Dec 30 11:13:12 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:12,191 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55588,localport=2575]

Dec 30 11:13:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1722) start AuditScheduler.execute()

Dec 30 11:13:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1722) finished AuditScheduler.execute()

Dec 30 11:13:22 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:22,191 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55592,localport=2575]

Dec 30 11:13:24 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:24,456 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.124,port=51418,localport=11112]

Dec 30 11:13:28 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:28,595 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=50892,localport=11112]

Dec 30 11:13:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:32,207 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55594,localport=2575]

Dec 30 11:13:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:32,303 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-585) start ExportScheduler.execute()

Dec 30 11:13:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:32,304 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-585) finished ExportScheduler.execute()

Dec 30 11:13:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:13:32,806 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=46541,localport=11112]

Dec 30 11:14:01 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:01,860 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55606,localport=2575]

Dec 30 11:14:07 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:07,938 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=38517,localport=11112]

Dec 30 11:14:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:09,452 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-575) start IANScheduler.execute()

Dec 30 11:14:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:09,453 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-575) finished IANScheduler.execute()

Dec 30 11:14:11 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:11,880 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55612,localport=2575]

Dec 30 11:14:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-112) start AuditScheduler.execute()

Dec 30 11:14:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-112) finished AuditScheduler.execute()

Dec 30 11:14:21 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:21,880 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55618,localport=2575]

Dec 30 11:14:27 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:27,980 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=50958,localport=11112]

Dec 30 11:14:31 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:31,895 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55622,localport=2575]

Dec 30 11:14:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:32,304 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-992) start ExportScheduler.execute()

Dec 30 11:14:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:32,305 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-992) finished ExportScheduler.execute()

Dec 30 11:14:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:32,580 INFO [org.dcm4chee.arc.delete.impl.DeleteRejectedInstancesScheduler] (EE-ManagedScheduledExecutorService-default-Thread-65) start DeleteRejectedInstancesScheduler.execute()

Dec 30 11:14:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:32,581 INFO [org.dcm4chee.arc.delete.impl.DeleteRejectedInstancesScheduler] (EE-ManagedScheduledExecutorService-default-Thread-65) finished DeleteRejectedInstancesScheduler.execute()

Dec 30 11:14:43 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:43,055 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=44245,localport=11112]

Dec 30 11:14:54 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:14:54,476 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.124,port=51428,localport=11112]

Dec 30 11:15:02 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:02,561 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55640,localport=2575]

Dec 30 11:15:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:09,453 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-338) start IANScheduler.execute()

Dec 30 11:15:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:09,454 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-338) finished IANScheduler.execute()

Dec 30 11:15:12 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:12,581 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55646,localport=2575]

Dec 30 11:15:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:15,938 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-999) start AuditScheduler.execute()

Dec 30 11:15:15 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:15,939 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-999) finished AuditScheduler.execute()

Dec 30 11:15:16 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:16,809 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.3.10,port=60909,localport=11112]

Dec 30 11:15:18 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:18,195 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=41299,localport=11112]

Dec 30 11:15:22 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:22,581 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55650,localport=2575]

Dec 30 11:15:27 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:27,956 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/172.16.202.10,port=51031,localport=11112]

Dec 30 11:15:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:32,305 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-998) start ExportScheduler.execute()

Dec 30 11:15:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:32,305 INFO [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-998) finished ExportScheduler.execute()

Dec 30 11:15:32 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:32,598 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55652,localport=2575]

Dec 30 11:15:53 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:53,328 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Accept connection Socket[addr=/10.156.1.24,port=36295,localport=11112]

Dec 30 11:15:55 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:55,155 INFO [org.dcm4chee.arc.delete.impl.PurgeStorageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-113) start PurgeStorageScheduler.execute()

Dec 30 11:15:55 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:15:55,156 INFO [org.dcm4chee.arc.delete.impl.PurgeStorageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-113) finished PurgeStorageScheduler.execute()

Dec 30 11:16:02 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:16:02,255 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Accept connection Socket[addr=/10.156.1.21,port=55664,localport=2575]

Dec 30 11:16:09 pacs_cph1 standalone.sh[1461]: #033[0m#033[0m11:16:09,454 INFO [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1729) start IANScheduler.execute()

fredag den 15. november 2019 kl. 15.47.10 UTC+1 skrev Niels Wahlgreen:

Gunter Zeilinger

unread,

Dec 30, 2019, 8:43:01 AM12/30/19

to dcm...@googlegroups.com

Have you followed:

13. Enable property replacement in deployment descriptors by setting attribute spec-descriptor-property-replacement of the ee subsystem to true, and adjust the managed-executor-services and the managed-scheduled-executor-service configuration of the ee subsystem to avoid thread-pool related issues on long running tasks or heavy load using JBoss CLI - you may configure a larger maximal number of threads than 100 according your needs:

[standalone@localhost:9990 /] /subsystem=ee:write-attribute(name=spec-descriptor-property-replacement,value=true)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:undefine-attribute(name=hung-task-threshold)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=long-running-tasks,value=true)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=core-threads,value=2)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=max-threads,value=100)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=queue-length,value=0)
[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=default:undefine-attribute(name=hung-task-threshold)
[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=def

How many associations are shown open in the monitor tab of the UI?

You may monitor the number of threads and heap memory in the Wildfly Admin console: Runtime -> Server -> Status, or by using JBOSS CLI:

$ jboss-cli -c "/core-service=platform-mbean/type=threading:read-resource(include-runtime=true)"

$ jboss-cli -c "/core-service=platform-mbean/type=memory:read-resource(include-runtime=true)"

You may also attach VisualVM:

$ visualvm --cp:a $WILDFLY_HOME/bin/client/jboss-cli-client.jar --openjmx service:jmx:remote+http://<archive-host>:9990

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/75ef8e44-6bb5-418a-bccb-5ed0ceffaf4c%40googlegroups.com.

Niels Wahlgreen

unread,

Dec 30, 2019, 9:17:12 AM12/30/19

to dcm...@googlegroups.com, Martin Christensen

Dear Gunter,

Thank you very very much.

It looks like we didn’t follow step 13 of the installation, since some of thes evalues were not set.I have configured them now.

We will look into it on January 2, when the system is under heavy load again and share the results here. But this looks like it could be the missing piece of our puzzle.

Have a happy new year.

Med venlig hilsen / Best regards

Niels Wahlgreen
Senior IT Consultant & Funder, Cand. Merc. (dat.)

Wahlgreen IT
Vadstrupvej 53 | DK-2880 Bagsværd
D: +45 70 23 50 45 | M: +45 26 34 60 80
E: ni...@wahlgreen.dk | W: www.wahlgreen.dk

Alle priser er ekskl. moms. Vi tager forbehold for prisændringer og/eller tastefejl.
Vores generelle betingelser er gældende. Du kan læse dem her.

Fra: 'Gunter Zeilinger' via dcm4che <dcm...@googlegroups.com>
Svar til: "dcm...@googlegroups.com" <dcm...@googlegroups.com>
Dato: mandag den 30. december 2019 kl. 14.43
Til: "dcm...@googlegroups.com" <dcm...@googlegroups.com>
Emne: Re: [dcm4che-group] Re: DCM4CHEE stops processing requests

Have you followed:

13. Enable property replacement in deployment descriptors by setting attribute spec-descriptor-property-replacement of the ee subsystem to true, and adjust the managed-executor-services and the managed-scheduled-executor-service configuration of the ee subsystem to avoid thread-pool related issues on long running tasks or heavy load using JBoss CLI - you may configure a larger maximal number of threads than 100 according your needs:

[standalone@localhost:9990 /] /subsystem=ee:write-attribute(name=spec-descriptor-property-replacement,value=true)

[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:undefine-attribute(name=hung-task-threshold)

[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=long-running-tasks,value=true)

[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=core-threads,value=2)

[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=max-threads,value=100)

[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=queue-length,value=0)

[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=default:undefine-attribute(name=hung-task-threshold)

[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=def

How many associations are shown open in the monitor tab of the UI?

You may monitor the number of threads and heap memory in the Wildfly Admin console: Runtime -> Server -> Status, or by using JBOSS CLI:

$ jboss-cli -c

$ jboss-cli -c "/core-service=platform-mbean/type=memory:read-resource(include-runtime=true)"

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/3fu0rJy6V9a5kzlg42WvCoFvDqft0nCiYf2apqh71QZ0jFojyBZ5Ce9-K3XMdAOuG52C0AaCuEkig6WZa9cm9EZV3P9MdoZXHIOwbbSsJlA%3D%40protonmail.com.

Gunter Zeilinger

unread,

Dec 30, 2019, 2:44:26 PM12/30/19

to dcm...@googlegroups.com

The command to get threading runtime information got truncated. Should be:

Niels Wahlgreen

unread,

Jan 2, 2020, 9:22:42 AM1/2/20

to dcm...@googlegroups.com

Hi Gunther,

We only had one CT scanning today, but we have been stress testing the PACS following the changes you suggested and there hasn’t been a single problem. So everything looks good so far. Time will tell, if it is completely resolved, but I am optimistic about that, looking at the results from today.

Thanks a lot.

Med venlig hilsen / Best regards

Niels Wahlgreen
Senior IT Consultant & Founder, Cand.Merc.(dat.)

Wahlgreen IT
Vadstrupvej 53 | DK-2880 Bagsværd
D: +45 7023 5045 | M: +45 2634 6080
E: ni...@wahlgreen.dk | W: www.wahlgreen.dk

Alle priser er ekskl. moms. Vi tager forbehold for prisændringer og/eller tastefejl.
Vores generelle betingelser er gældende. Du kan læse dem her.

Fra: 'Gunter Zeilinger' via dcm4che <dcm...@googlegroups.com>
Sendt: 30. december 2019 20:44
Til: dcm...@googlegroups.com
Emne: Re: [dcm4che-group] Re: DCM4CHEE stops processing requests

The command to get threading runtime information got truncated. Should be:

$ jboss-cli -c "/core-service=platform-mbean/type=threading:read-resource(include-runtime=true)"

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/h4PPpVe2ofrbiIOjNgeLXVck53FQrERdcIM474o5ZID64z9RnAJIXwzUuWgNHOTWf7-xrVxw0A98IFixCLbE1BWfvbi2WEGbbOOnYXMJzJY%3D%40protonmail.com.

Reply all

Reply to author

Forward