Error when executing pull notifications in xds sender module

Ask OpenMRS
1

Application Name: iSanteplus - OpenHIM - XDS-Sender

I am using the xds-sender module and I have configured it to begin searching for results posted to my openHIE system. The service is scheduled, but when I look in the log nothing is getting sent to openHIE as we are receiving the following error.

ERROR - TimerSchedulerTask.run(50) |2020-10-30 15:43:19,002| FATAL ERROR:     Task [class org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper] failed due to exception [java.lang.IllegalStateException]
java.lang.IllegalStateException: No marshaller registered. Check configuration of WebServiceTemplate.
	at org.springframework.ws.client.core.WebServiceTemplate$2.doWithMessage(WebServiceTemplate.java:396)
	at org.springframework.ws.client.core.WebServiceTemplate.doSendAndReceive(WebServiceTemplate.java:590)
	at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:555)
	at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:390)
	at org.openmrs.module.xdssender.api.notificationspullpoint.impl.NotificationsPullPointClientImpl.getResponse(NotificationsPullPointClientImpl.java:62)
	at org.openmrs.module.xdssender.api.notificationspullpoint.impl.NotificationsPullPointClientImpl.getNewMessages(NotificationsPullPointClientImpl.java:40)
	at org.openmrs.module.xdssender.api.scheduler.PullNotificationsTask.execute(PullNotificationsTask.java:26)
	at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:67)
	at org.openmrs.scheduler.timer.TimerSchedulerTask.execute(TimerSchedulerTask.java:94)
	at org.openmrs.api.context.Daemon$2.run(Daemon.java:135)

Has anyone encountered this error before? @ohinc it seems you were the original developer of this piece, are you able to help us with any ideas why this is happening?

cc @nathaelf @pmanko @moshon @dkayiwa

1 Like
2

What value do you have for the global property/setting named xdssender.notificationsPullPoint.endpoint?

3

https://sedish.net:5001/dsub

4

Is it the xds module expected configuration end point url for pulling? Are you able to access it in your browser?

5

I am not sure what endpoint it should be - this was just my best guess - do you know in the OpenHIE architecture where the mongo db pull point for HL7 result notifications should be?

6

Is the goal to send data to sedish?

7

@dkayiwa we figured out the endpoint and what was missing , but now we are having an issue with the xds-sender service sending the wrong content-length with the SOAP message, this causes the request sent to openhim to timeout - has anyone run into this issue before?

8

Not any one that i can remember. Do you mind sharing the error log via pastebin.com?

1 Like