java.io.IOException: Message too long when trying to download a study

[Paul]

Hello!

It happens with dcm4chee-arc-5.23.2 on ubuntu 20.04 LTS

The study in question can be stored successfully via storescu or the web interface.

When attempting downloading the study via the web or movescu the following errors appear in logs:

2022-02-10 11:42:34,670 WARN [org.dcm4chee.arc.audit.AuditService] (EE-ManagedScheduledExecutorService-default-Thread-98) Failed to mark [AuditSpoolFile=/opt/wildfly/standalone/data/audit-spool/Audit+Logger/STORE_CREA-STORESCU-DCM4CHEE-1.2.826.0.1.3680043.8.498.70561287453158446744711681555795206814_ERROR] of [AuditLogger=Audit Logger] as failed.
: java.io.IOException: Message too long
at java.base/java.net.PlainDatagramSocketImpl.send(Native Method)
at java.base/java.net.DatagramSocket.send(DatagramSocket.java:695)
at org.dcm4ch...@5.23.3//org.dcm4che3.net.audit.AuditLogger$UDPConnection.sendMessage(AuditLogger.java:1150)
at org.dcm4ch...@5.23.3//org.dcm4che3.net.audit.AuditLogger.sendMessage(AuditLogger.java:754)
at org.dcm4ch...@5.23.3//org.dcm4che3.net.audit.AuditLogger.write(AuditLogger.java:730)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService.emitAuditMessage(AuditService.java:1039)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService.auditStoreError(AuditService.java:616)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService.auditStoreOrWADORetrieve(AuditService.java:622)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService.aggregateAuditMessage(AuditService.java:125)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService.auditAndProcessFile(AuditService.java:417)
at jdk.internal.reflect.GeneratedMethodAccessor139.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.jboss...@3.1.6.Final//org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
at org.jboss...@3.1.6.Final//org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditService$Proxy$_$$_WeldClientProxy.auditAndProcessFile(Unknown Source)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear//org.dcm4chee.arc.audit.AuditScheduler.execute(AuditScheduler.java:116)
at deployment.dcm4chee-arc-ear-5.23.3-psql.ear.dcm4chee-arc-service-5.23.3.jar//org.dcm4chee.arc.Scheduler.run(Scheduler.java:78)
at org.jbo...@23.0.2.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:178)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:360)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:511)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227)

2022-02-10 11:42:34,671 INFO [org.dcm4che3.net.audit.AuditLogger] (EE-ManagedScheduledExecutorService-default-Thread-98) Send audit message to /127.0.0.1:514
2022-02-10 11:42:34,674 INFO [org.dcm4che3.net.audit.AuditLogger] (EE-ManagedScheduledExecutorService-default-Thread-98) Send audit message to /127.0.0.1:514
2022-02-10 11:42:34,674 INFO [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-98) finished AuditScheduler.execute()
2022-02-10 11:42:35,433 INFO [org.dcm4che3.net.Dimse] (EE-ManagedScheduledExecutorService-default-Thread-113) DCM4CHEE<-SCU_SCU(123) << 1:C-MOVE-RSP[pcid=5, remaining=802, completed=0, failed=2273, warning=0, status=ff00H
cuid=1.2.840.10008.5.1.4.1.2.2.2 - Study Root Query/Retrieve Information Model - MOVE
tsuid=1.2.840.10008.1.2 - Implicit VR Little Endian]
2022-02-10 11:42:35,434 WARN [org.dcm4chee.arc.store.scu.impl.RetrieveTaskImpl] (EE-ManagedScheduledExecutorService-default-Thread-113) DCM4CHEE<-SCU_SCU(123): Unable to send C-GET or C-MOVE RSP on association to SCU_SCU: java.io.EOFException
at org.dcm4...@5.23.3//org.dcm4che3.util.StreamUtils.readFully(StreamUtils.java:74)
at org.dcm...@5.23.3//org.dcm4che3.net.PDUDecoder.readFully(PDUDecoder.java:225)
at org.dcm...@5.23.3//org.dcm4che3.net.PDUDecoder.nextPDU(PDUDecoder.java:159)
at org.dcm...@5.23.3//org.dcm4che3.net.Association$2.run(Association.java:571)
at org.jbo...@23.0.2.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledRunnable.run(ControlPointUtils.java:125)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:117)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227)

Seems like some packages hit the PDU limit. All other studies can be stored and downloaded without problem, it's not clear how to debug the issue.

Thanks.

[Gunter Zeilinger]

The exception only concerns the emission of the Audit Message - which seems to large to can be sent by UDP syslog -  which should not affect the actual retrieve. But you may disable the Audit Logger by setting its property installed=false.

[Paul]

Thanks, switching off the Audit Logger helped me to get rid of the message length error but the study still can't be downloaded. I will try to gather more information and post a new message in the group if I can't fix the problem.