Auto forwarding of received images in dcm4chee-arc-light

[Deeps]

Hi,

 Someone please help me with the auto forwarding of received images in dcm4che-arc-light. I have created a new AET (STORESCP with port 11115, localhost ) for destination and followed the steps in the link https://github.com/dcm4che/dcm4chee-arc-light/wiki/Export-Rule .  Then added the Export Task Polling Interval as PT1M as specified in https://github.com/dcm4che/dcm4chee-arc-light/wiki/Forwarding-of-received-instances . In a new terminal window started the TCP listener using the command storescp -b STORESCP:11115. Then sent an image to dcm4chee-arc-light. But this is not forwarded to STORESCP. What I am missing in this. Please help.

[vrinda nayak]

What do you see in the server logs ?

Do you see the export task in Monitoring page -> Export Tab ?

[Deeps]

Hi,

4.		MR	1.2.826.0.1.3680043.2.1006.20190930093213943584985	1	STORESCP	FAILED	11		0.0000 s	dcm4chee-arc
5.			1.2.826.0.1.3680043.2.1006.20190930093213943584985		CalculateQueryAttributes	COMPLETED			0.0000 s	dcm4chee-arc
6.			1.2.826.0.1.3680043.2.1006.20190930093213943584985		CalculateStudySize	COMPLETED			0.0000 s	dcm4chee-arc

This is the message I got for a particular image from monitoring page -> Export tab.

Today I tried sending one more image and in server log ExportTask got created.

10:28:31,401 INFO  [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedExecutorService-default-Thread-3217) org.dcm4chee.arc.store.impl.StoreContextImpl@10890e76: Created IanTask[pk=30, deviceName=dcm4chee-arc, studyInstanceUID=1.2.826.0.1.3680043.2.1006.20190930096765768795663, scheduledTime=Wed Dec 11 10:33:31 IST 2019]
10:28:31,406 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedExecutorService-default-Thread-3217) Create ExportTask[pk=422, exporterID=STORESCP, studyUID=1.2.826.0.1.3680043.2.1006.20190930096765768795663, seriesUID=*, objectUID=*]
10:28:31,415 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedExecutorService-default-Thread-3217) Create ExportTask[pk=423, exporterID=CalculateQueryAttributes, studyUID=1.2.826.0.1.3680043.2.1006.20190930096765768795663, seriesUID=1.2.840.113619.2.80.4246227874.7760.1532545464765765, objectUID=1.2.840.113619.2.80.4246227874.77656546576897]
10:28:31,427 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedExecutorService-default-Thread-3217) Create ExportTask[pk=424, exporterID=CalculateStudySize, studyUID=1.2.826.0.1.3680043.2.1006.20190930096765768795663, seriesUID=1.2.840.113619.2.80.4246227874.7760.1532545464765765, objectUID=1.2.840.113619.2.80.4246227874.77656546576897]

[Deeps]

The configurations which I made are given below:-

1) Created AET by giving STORESCP, 11115 port and localhost.

2) Created DICOM Exporter
Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Go to its Child objects and select + Add a new Exporter against the field Exporter Descriptor.
Entered the values for Exporter ID -STORESCP , URI - STORESCP,  Queue Name - Export1, Export Priority -4,  Application Entity (AE) title - APACSVNA(modified name of DCM4CHEE). Didn't mention any export schedule to process the export task immediately and Saved the configurations.

3) Created Export Rule
Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Go to its Child objects and select + Add a new Export Rule against the field Export Rule.
Enter the values for Name -Forward to STORESCP , Export Entity - Study, Exporter ID - STORESCP and Export Delay - PT1M and Saved.

4) Then modified Export task polling interval
Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Value of the field Export Task Polling Interval modified as PT1M.










 

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[vrinda nayak]

Value for the URI field in Exporter Descriptor is wrong and hence it FAILED. Change the value from STORESCP to dicom:STORESCP and retry.

[Deeps]

Thank you Vrinda for the reply. But that didnt work for me. I changed the URI field as dicom:STORESCP and saved the configuration. Tried sending a new image. But nothing came in the storescp listener window. What is the time limit it will take to export? Is it the value of Export Task Polling Interval?

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[vrinda nayak]

Yes it is the duration you configured for the polling interval and any delay in export rule. If you see the task in Monitoring page -> Export tab, expand on and see what is the error/outcome message. Also check the server log.

[Deeps]

The image which I sent today is still showing status - TO SCHEDULE. The below error message is from yesterday's failed instance.

Annotation member value org.dcm4chee.arc.conf.NamedQualifier.value must not be null. This is the error message got after expanding Monitoring page -> Export tab.

In server log:

2019-12-10 12:24:23,440 WARN  [org.dcm4chee.arc.export.mgt.impl.ExportManagerMDB] (Thread-125 (ActiveMQ-client-global-threads)) Failed to process ActiveMQMessage[ID:e5e4ca3d-1b19-11ea-ba93-b083fe931f92]:PERSISTENT/ClientMessageImpl[messageID=55835069056, durable=true, address=jms.queue.Export1,userID=e5e4ca3d-1b19-11ea-ba93-b083fe931f92,properties=TypedProperties[RequesterUserID=admin,__AMQ_CID=e5e4a329-1b19-11ea-ba93-b083fe931f92,RequesterHostName=192.168.17.30,StudyInstanceUID=1.2.826.0.1.3680043.2.1006.201909555555555555555,_AMQ_ROUTING_TYPE=1,ExporterID=STORESCP,RequestURI=/dcm4chee-arc/aets/APACSVNA/rs/studies/1.2.826.0.1.3680043.2.1006.201909555555555555555/export/STORESCP]]: java.lang.IllegalArgumentException: Annotation member value org.dcm4chee.arc.conf.NamedQualifier.value must not be null
    at javax.enterprise.util.AnnotationLiteral.getMemberValue(AnnotationLiteral.java:279)
    at javax.enterprise.util.AnnotationLiteral.hashCode(AnnotationLiteral.java:246)
    at java.util.HashMap.hash(HashMap.java:339)
    at java.util.HashMap.put(HashMap.java:612)
    at java.util.HashSet.add(HashSet.java:220)
    at org.jboss.weld.util.Beans.mergeInQualifiers(Beans.java:393)
    at org.jboss.weld.bean.builtin.FacadeInjectionPoint.<init>(FacadeInjectionPoint.java:43)
    at org.jboss.weld.bean.builtin.InstanceImpl.selectInstance(InstanceImpl.java:164)
    at org.jboss.weld.bean.builtin.InstanceImpl.select(InstanceImpl.java:140)
    at org.jboss.weld.bean.builtin.InstanceImpl.select(InstanceImpl.java:72)
    at org.dcm4chee.arc.exporter.ExporterFactory.getExporter(ExporterFactory.java:21)
    at org.dcm4chee.arc.exporter.ExporterFactory$Proxy$_$$_WeldClientProxy.getExporter(Unknown Source)
    at org.dcm4chee.arc.export.mgt.impl.ExportManagerMDB.onMessage(ExportManagerMDB.java:104)
    at sun.reflect.GeneratedMethodAccessor171.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102)
    at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
    at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:216)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.notSupported(CMTTxInterceptor.java:345)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:142)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
    at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81)
    at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:242)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618)
    at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
    at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
    at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
    at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
    at org.dcm4chee.arc.export.mgt.impl.ExportManagerMDB$$$view49.onMessage(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor171.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139)
    at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)
    at org.dcm4chee.arc.export.mgt.impl.ExportManagerMDB$$$endpoint23.onMessage(Unknown Source)
    at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:319)
    at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1031)
    at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)
    at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1154)
    at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
    at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
    at org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

Check the URI of your STORESCP Exporter. Should be "dicom:<aet-of-storescp>"

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/b46b34af-910a-4925-bd1a-1c7cf7a95671%40googlegroups.com.

[Deeps]

Thank you Vrinda and Gunterze. The image which I tried sending after changing the URI field came to STORESCP listener window. The status also changed to COMPLETED under Monitoring -> Export Tab.

Is there something to do with the error:

16:01:11,149 WARN  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Failed to query Export Task Info for ExportTask[pk=423, exporterID=CalculateQueryAttributes, studyUID=1.2.826.0.1.3680043.2.1006.20190930096765768795663, seriesUID=1.2.840.113619.2.80.4246227874.7760.1532545464765765, objectUID=1.2.840.113619.2.80.4246227874.77656546576897] - : java.lang.NullPointerException
    at org.dcm4chee.arc.query.impl.QueryServiceImpl.queryExportTaskInfo(QueryServiceImpl.java:267)
    at org.dcm4chee.arc.query.impl.QueryServiceImpl$Proxy$_$$_WeldClientProxy.queryExportTaskInfo(Unknown Source)
    at org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB.scheduleExportTask(ExportManagerEJB.java:260)
    at org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB.scheduleExportTasks(ExportManagerEJB.java:195)
    at sun.reflect.GeneratedMethodAccessor111.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89)
    at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102)
    at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

    at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

    at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
    at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

    at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:362)
    at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:144)

    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
    at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81)
    at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

    at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)

    at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618)
    at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
    at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
    at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
    at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
    at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
    at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)

    at org.dcm4chee.arc.export.mgt.ExportManager$$$view50.scheduleExportTasks(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor110.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)

    at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410)
    at org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134)
    at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
    at org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68)
    at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106)
    at org.dcm4chee.arc.export.mgt.impl.ExportManager$1469038282$Proxy$_$$_Weld$EnterpriseProxy$.scheduleExportTasks(Unknown Source)
    at org.dcm4chee.arc.export.mgt.impl.ExportScheduler.execute(ExportScheduler.java:50)
    at org.dcm4chee.arc.Scheduler.run(Scheduler.java:77)
    at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:158)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
    at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

    at java.lang.Thread.run(Thread.java:748)
    at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[vrinda nayak]

The error you get for CalculateQueryAttributes exporter related task is unrelated with forwarding of objects. You changed the AE Title from DCM4CHEE to <your-AET>. In newer version of archive it gets reflected automatically wherever DCM4CHEE was being used. You may have to manually change in these exporters to reflect <your-AET>

[Deeps]

Okay Vrinda. Thank you. I am still facing issues in exporting images. I sent 1 more image and createdTime - 2019-12-11T16:38:11.000+0530. scheduledTime 2019-12-11T16:39:11.000+0530. Now the time is 17:43. Status is still -  TO SCHEDULE.

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Deeps]

Hi,

     The export task is working properly. The only problem is that the export task is not being done based on the configured polling interval which is PT1M and Export Delay PT1M. 

Export Task Polling Interval is also PT1M. I have sent an image at 18:59:37 (11-12-2019). But the export task is carried out at 00:32:14 (12-12-2019).  Once an image is sent the scheduled time will be shown as created time + 1 minute.

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

Check the state of the JMS. Particularly the message count


If the queue is working properly, the delay between the scheduled time and the processing data time is lesser than configured pollling interval:

and the corresponding server.log messages looks like:

2019-12-13 09:24:55,221 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule Task[id=ID:0ac889e9-1d82-11ea-9ad7-e47fb220e0f2] at Queue Export1

2019-12-13 09:24:55,449 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule ExportTask[pk=3, exporterID=STORESCP, studyUID=1.2.840.113674.1115.261.200, seriesUID=1.2.840.113674.1115.261.182.300, objectUID=*]

2019-12-13 09:24:55,454 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule Task[id=ID:0aed9e1a-1d82-11ea-9ad7-e47fb220e0f2] at Queue Export1

2019-12-13 09:24:55,464 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (Thread-23 (ActiveMQ-client-global-threads)) Start processing Task[id=ID:0ac889e9-1d82-11ea-9ad7-e47fb220e0f2] from Queue Export1 with Status: SCHEDULED

2019-12-13 09:24:55,521 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) finished ExportScheduler.execute()

2019-12-13 09:24:55,522 INFO  [org.dcm4che3.net.Connection] (Thread-23 (ActiveMQ-client-global-threads)) Initiate connection from /0.0.0.0:0 to localhost:11115

2019-12-13 09:24:55,522 INFO  [org.dcm4che3.net.Connection] (Thread-23 (ActiveMQ-client-global-threads)) Established connection Socket[addr=localhost/127.0.0.1,port=11115,localport=54221]

2019-12-13 09:24:55,522 DEBUG [org.dcm4che3.net.Association] (Thread-23 (ActiveMQ-client-global-threads)) /127.0.0.1:54221->localhost/127.0.0.1:11115(3): enter state: Sta4 - Awaiting transport connection o

pening to complete

2019-12-13 09:24:55,522 INFO  [org.dcm4che3.net.Association] (Thread-23 (ActiveMQ-client-global-threads)) DCM4CHEE->STORESCP(3) << A-ASSOCIATE-RQ

:

2019-12-13 09:24:55,570 INFO  [org.dcm4che3.net.Association] (Thread-23 (ActiveMQ-client-global-threads)) DCM4CHEE->STORESCP(3) << A-RELEASE-RQ

2019-12-13 09:24:55,570 DEBUG [org.dcm4che3.net.Association] (Thread-23 (ActiveMQ-client-global-threads)) DCM4CHEE->STORESCP(3): enter state: Sta7 - Awaiting A-RELEASE-RP PDU

2019-12-13 09:24:55,570 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-15) DCM4CHEE->STORESCP(3) >> A-RELEASE-RP

2019-12-13 09:24:55,570 INFO  [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-15) DCM4CHEE->STORESCP(3): close Socket[addr=localhost/127.0.0.1,port=11115,localport=54221]

2019-12-13 09:24:55,571 DEBUG [org.dcm4che3.net.Association] (EE-ManagedExecutorService-default-Thread-15) DCM4CHEE->STORESCP(3): enter state: Sta1 - Idle

2019-12-13 09:24:55,581 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (Thread-23 (ActiveMQ-client-global-threads)) Finished processing of Task[id=ID:0ac889e9-1d82-11ea-9ad7-e47fb220e0f2] at Queue Export1 with Status COMPLETED

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/8fa1a62e-773f-4e35-831a-e7a296a44e14%40googlegroups.com.

[Deeps]

Thank you for your response Gunterze. We have given Export4 as JMS Queue Name and sent a new image.  The created time is 17:49:05 and the scheduled time is 17:50:05. Now the time is 18:02:10 and it is still under TO SCHEDULE status. Under  HAL Management Console(Export4) there are no message count given.

Messages

• Messages Added 0
• Message Count 0
• Delivering Count 0
• Scheduled Count 0

Attaching the screenshots.

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

Check for server.log messages of ExportScheduler:

$ grep ExportScheduler ~/wildfly-18.0.0.Final/standalone/log/server.log | tail

2019-12-13 11:18:56,095 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-15) start ExportScheduler.execute()

2019-12-13 11:18:56,096 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-15) finished ExportScheduler.execute()

2019-12-13 11:19:56,096 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) start ExportScheduler.execute()

2019-12-13 11:19:56,097 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) finished ExportScheduler.execute()

2019-12-13 11:20:56,098 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-3) start ExportScheduler.execute()

2019-12-13 11:20:56,099 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-3) finished ExportScheduler.execute()

2019-12-13 11:21:56,100 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-5) start ExportScheduler.execute()

2019-12-13 11:21:56,102 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-5) finished ExportScheduler.execute()

2019-12-13 11:22:56,102 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-7) start ExportScheduler.execute()

2019-12-13 11:22:56,103 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-7) finished ExportScheduler.execute()

Should match with your configuration of

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/371b2eac-933c-4092-816d-eadbff6f1372%40googlegroups.com.

[Deeps]

Sorry Gunterze, I couldn't find any details about ExportScheduler in the server.log. These are the details in my log.

2019-12-13 23:21:23,385 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule ExportTask[pk=455, exporterID=STORESCP, studyUID=1.2.826.0.1.3680043.2.1006.201909300980809.45899, seriesUID=*, objectUID=*]
2019-12-13 23:21:23,418 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule Task[id=ID:2d5421e2-1dd1-11ea-8c45-b083fe931f92] at Queue Export4
2019-12-13 23:21:23,506 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule ExportTask[pk=456, exporterID=CalculateQueryAttributes, studyUID=1.2.826.0.1.3680043.2.1006.201909300980809.45899, seriesUID=1.2.840.113619.2.80.4246227874.7760.1569435454543.2353, objectUID=1.2.840.113619.2.80.4246227874.7760.43243432.423432]
2019-12-13 23:21:23,510 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule Task[id=ID:2d633d13-1dd1-11ea-8c45-b083fe931f92] at Queue Export4
2019-12-13 23:21:23,513 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule ExportTask[pk=457, exporterID=CalculateStudySize, studyUID=1.2.826.0.1.3680043.2.1006.201909300980809.45899, seriesUID=1.2.840.113619.2.80.4246227874.7760.1569435454543.2353, objectUID=1.2.840.113619.2.80.4246227874.7760.43243432.423432]
2019-12-13 23:21:23,518 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-2) Schedule Task[id=ID:2d644e84-1dd1-11ea-8c45-b083fe931f92] at Queue Export4

2019-12-13 23:56:30,637 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-1) Delete Task[id=ID:0435cd69-1d08-11ea-b989-b083fe931f92] from Queue Export4
2019-12-13 23:56:30,650 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-1) Delete Task[id=ID:0436deda-1d08-11ea-b989-b083fe931f92] from Queue Export4
2019-12-13 23:56:30,658 INFO  [org.dcm4chee.arc.qmgt.impl.PurgeQueueMessageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) Deleted 2 COMPLETED messages from queue Export4
2019-12-13 23:56:30,689 INFO  [org.dcm4chee.arc.qmgt.impl.QueueManagerEJB] (EE-ManagedScheduledExecutorService-default-Thread-1) Delete Task[id=ID:04316098-1d08-11ea-b989-b083fe931f92] from Queue Export1
2019-12-13 23:56:30,701 INFO  [org.dcm4chee.arc.qmgt.impl.PurgeQueueMessageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) Deleted 1 COMPLETED messages from queue Export1

Values configured:

Export Task Polling Interval is PT1M

Export Task Fetch Size 100

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

Starting with v5.19.0 you should see

2019-12-13 11:18:56,095 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-15) start ExportScheduler.execute()

2019-12-13 11:18:56,096 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-15) finished ExportScheduler.execute()

in the server.log. Otherwise something is wrong with your Wildfly instance, particular one of the thread pools may have run out of the configured maximal number of threads.

Perhaps the issue is caused by #1496 - I realized, that we forgot to remove

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

from the Installation description.
You should also set

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

which was also missing in the description.

I will provide a CLI script in v5.20.0 for that adjustments.

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/36168951-fcd7-4bb5-bdc3-3841203ec280%40googlegroups.com.

[Gunter Zeilinger]

Correction:

You should also set

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

(not **jboss**-descriptor-property-replacement).

Sent with ProtonMail Secure Email.

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

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

[Deeps]

Hi Gunter,

              After making the modifications the corresponding values in dcm4chee-arc.xml is given below. We are using version 5.18.0. After modification tried sending an image. But that also didnt get auto forwarded after specified Poll Interval of 1 minute.

<subsystem xmlns="urn:jboss:domain:ee:4.0">
            <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>
            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
...
 </subsystem>


<managed-scheduled-executor-services>
                    <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/>
                </managed-scheduled-executor-services>

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

Could not reproduce with latest version and

        <subsystem xmlns="urn:jboss:domain:ee:4.0">

            <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>

            <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>

            <concurrent>

                <context-services>

                    <context-service name="default" jndi-name="java:jboss/ee/concurrency/context/default" use-transaction-setup-provider="true"/>

                </context-services>

                <managed-thread-factories>

                    <managed-thread-factory name="default" jndi-name="java:jboss/ee/concurrency/factory/default" context-service="default"/>

                </managed-thread-factories>

                <managed-executor-services>

                    <managed-executor-service name="default" jndi-name="java:jboss/ee/concurrency/executor/default" context-service="default" long-running-tasks="true" core-threads="2" max-threads="100" keepalive-time="5000" queue-length="0"/>

                </managed-executor-services>

                <managed-scheduled-executor-services>

                    <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" keepalive-time="3000"/>

                </managed-scheduled-executor-services>

            </concurrent>

            <default-bindings context-service="java:jboss/ee/concurrency/context/default" datasource="java:jboss/datasources/ExampleDS" jms-connection-factory="java:jboss/DefaultJMSConnectionFactory" managed-executor-service="java:jboss/ee/concurrency/executor/default" managed-scheduled-executor-service="java:jboss/ee/concurrency/scheduler/default" managed-thread-factory="java:jboss/ee/concurrency/factory/default"/>

        </subsystem>

which also is the configuration of the Docker versions:

https://github.com/dcm4che-dockerfiles/dcm4chee-arc-psql/blob/master/configuration/dcm4chee-arc.xml#L274-L291

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/dad74767-06f9-4605-90b3-c058f1723dc1%40googlegroups.com.

[Gunter Zeilinger]

Correction:

        <subsystem xmlns="urn:jboss:domain:ee:4.0">

            <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>

            <concurrent>

...

Sent with ProtonMail Secure Email.

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

[Deeps]

I used the same configuration in my dcm4chee-arc.xml as you mentioned. But still facing the same issue. Image is not auto forwarded after 1 minute.

In the docker version(https://github.com/dcm4che-dockerfiles/dcm4chee-arc-psql/blob/master/configuration/dcm4chee-arc.xml#L274-L291)         <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement> is missing.

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

<jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement> is not necessary. Only

<spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>

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/fcbe0e7e-8c6e-4d67-a98b-fe58b8811588%40googlegroups.com.

[Deeps]

Hi Gunter,

              We upgraded dcm4chee-arc-light version to 5.19.1.

Followed the same steps:

1) Since STORESCP was already there in the list with 104 port, changed port to 11115.

2) Created DICOM Exporter
Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Go to its Child objects and select + Add a new Exporter against the field Exporter Descriptor.

Entered the values for Exporter ID -STORESCP , URI - dicom:STORESCP,  Queue Name - Export1, Export Priority -4,  Application Entity (AE) title -  DCM4CHEE. Didn't mention any export schedule to process the export task immediately and Saved the configurations.

3) Created Export Rule
Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Go to its Child objects and select + Add a new Export Rule against the field Export Rule.

Enter the values for Name -Forward to STORESCP , Export Entity - Series, Exporter ID - STORESCP and Export Delay - PT1M and Saved.

4) Then modified Export task polling interval

Go to Menu->Configuration, then on Devices page click on Edit of the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive Device. Value of the field Export Task Polling Interval modified as PT1M and Export Task Fetch Size is 100.

Tried sending an image. But it got auto forwarded after 5 hours.

Modified dcm4chee-arc.xml with values:

 <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>

...

<managed-scheduled-executor-services>
       <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" keepalive-time="3000"/>
</managed-scheduled-executor-services>

Restarted wildfly. Again tried sending an image and still not getting auto forwarded after 1 minute.

Now in the server.log details about  ExportScheduler is coming.

2019-12-24 12:12:11,335 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-3) start ExportScheduler.execute()
2019-12-24 12:12:11,337 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-3) finished ExportScheduler.execute()
2019-12-24 12:12:17,255 INFO  [org.dcm4chee.arc.qmgt.impl.PurgeQueueMessageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-4) start PurgeQueueMessageScheduler.execute()
2019-12-24 12:12:17,373 INFO  [org.dcm4chee.arc.qmgt.impl.PurgeQueueMessageScheduler] (EE-ManagedScheduledExecutorService-default-Thread-4) finished PurgeQueueMessageScheduler.execute()
2019-12-24 12:12:27,448 INFO  [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) start IANScheduler.execute()
2019-12-24 12:12:27,455 INFO  [org.dcm4chee.arc.ian.scu.IANScheduler] (EE-ManagedScheduledExecutorService-default-Thread-1) finished IANScheduler.execute()
2019-12-24 12:12:48,434 INFO  [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) start AuditScheduler.execute()
2019-12-24 12:12:48,434 INFO  [org.dcm4chee.arc.audit.AuditScheduler] (EE-ManagedScheduledExecutorService-default-Thread-2) finished AuditScheduler.execute()
2019-12-24 12:13:11,338 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-6) start ExportScheduler.execute()
2019-12-24 12:13:11,340 INFO  [org.dcm4chee.arc.export.mgt.impl.ExportScheduler] (EE-ManagedScheduledExecutorService-default-Thread-6) finished ExportScheduler.execute()

Am I missing out something? Why the auto forwarding is not happening after scheduled 1 minute? Please help.

On Tuesday, December 10, 2019 at 7:01:49 PM UTC+5:30, Deeps wrote:

[Gunter Zeilinger]

What's the status of the Export Tasks?

What's its scheduledTime shown in the UI?

What's the value in the DB? E.g.:

$ docker exec -it dcm4chee_db_1 psql pacsdb pacs -c "select scheduled_time from export_task";

     scheduled_time     

-------------------------

2019-12-26 09:29:53.716

...

Verify current time of the archive and in the DB container:

$ docker exec -it dcm4chee_db_1 date

Thu 26 Dec 2019 09:33:48 AM CET

$ docker exec -it dcm4chee_arc_1 date

Thu Dec 26 09:34:00 CET 2019

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/7160d887-7fc0-42b7-804d-589a3558b7b9%40googlegroups.com.

[Deeps]

Thank you so much for your help Gunter. Actually we had installed MYSQL5.7.9 on a docker. When checked the time in MYSQL it was showing wrong time. We corrected the MYSQL time and auto forwarding worked properly.  Thank you once again.