Pre fetch WADO objects -dcm4chee-arc-light

107 views
Skip to first unread message

Amms

unread,
Feb 12, 2020, 2:14:18 AM2/12/20
to dcm4che
 Hi,

           I am trying to prefetch WADO jpeg images during C-Move from external PACS to DCM4CHEE. For this I have configured simple use case and Storage as per https://github.com/dcm4che/dcm4chee-arc-light/wiki/Pre-fetch-of-WADO-objects.

        Attached the screenshot of the configuration done. After configured the details I performed a C-Move from my external PACS To DCM4CHEE . In the log the Export task is created and after 1 minute the task is sheduled > but later the task is failing with java.lang.NullPointerException

      Any suggestion to fix this issue ?


  Log details:


2020-02-11 19:30:07,874 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedExecutorService-default-Thread-49) Create ExportTask[pk=86, ExporterID=WADO-JPEG]
2020-02-11 19:32:02,110 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-1) Schedule Task[id=ID:13bd63f1-4cd7-11ea-9de2-b083fe9315dd] at Queue Export2
2020-02-11 19:32:02,228 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (Thread-27 (ActiveMQ-client-global-threads)) Start processing Task[id=ID:13bd63f1-4cd7-11ea-9de2-b083fe9315dd] from Queue Export2 with Status: SCHEDULED
2020-02-11 19:32:02,243 WARN  [org.dcm4chee.arc.export.mgt.impl.ExportManagerMDB] (Thread-27 (ActiveMQ-client-global-threads)) Failed to process ActiveMQMessage[ID:13bd63f1-4cd7-11ea-9de2-b083fe9315dd]:PERSISTENT/ClientMessageImpl[messageID=8589960886, durable=true, address=jms.queue.Export2,userID=13bd63f1-4cd7-11ea-9de2-b083fe9315dd,properties=TypedProperties[__AMQ_CID=00a3bd66-4cd4-11ea-9de2-b083fe9315dd,StudyInstanceUID=1.2.826.0.1.3680043.2.1006.2020024543545345453423,SeriesInstanceUID=1.2.840.113619.2.80.4246227874.7760.1564356546564,ExporterID=WADO-JPEG]]: java.lang.NullPointerException


    Thanks in advance
Storage.png
ExportRule.png
Exporter.png

Vrinda Nayak

unread,
Feb 12, 2020, 5:31:08 AM2/12/20
to dcm4che
Thanks for reporting this issue.
Reply all
Reply to author
Forward
0 new messages