Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
faziluddinsk
Contributor
Contributor

Getting exception "java.lang.RuntimeException: Rest response already sent." while building REST service

I am currently working on building a REST service, and everything looks good, but in the final component tRestResponse which returns the response back to the client, errors out with below exception. I am currently in a limbo as to what can be done to fix it. Please help.

0695b00000JOYfMAAX.png

java.lang.RuntimeException: Rest response already sent.

at dco_talend_services.svc_processeventnotificationstomc_0_1.svc_processEventNotificationsToMC.tFixedFlowInput_10Process(svc_processEventNotificationsToMC.java:19645) [classes/:?]

at dco_talend_services.svc_processeventnotificationstomc_0_1.svc_processEventNotificationsToMC.tFixedFlowInput_9Process(svc_processEventNotificationsToMC.java:31846) [classes/:?]

at dco_talend_services.svc_processeventnotificationstomc_0_1.svc_processEventNotificationsToMC.CreditCardExpiring_1_tFixedFlowInput_1Process(svc_processEventNotificationsToMC.java:17542) [classes/:?]

at dco_talend_services.svc_processeventnotificationstomc_0_1.svc_processEventNotificationsToMC.CreditCardExpiring_1_tWriteJSONField_1_InProcess(svc_processEventNotificationsToMC.java:15214) [classes/:?]

at dco_talend_services.svc_processeventnotificationstomc_0_1.svc_processEventNotificationsToMC$1ThreadXMLField_CreditCardExpiring_1_tWriteJSONField_1_Out.run(svc_processEventNotificationsToMC.java:14832) [classes/:?]

Labels (6)
2 Replies
gjeremy1617088143

Hi @Not defined Not defined​ , maybe you have multiple conditions checked so you have multiple responses

desactivate the tRestRespoonse and see in the last tLogRow if you have muliple responses and from wich flow they are.

Send me love and kudos

Anonymous
Not applicable

I my goodness... this is a terrible job design.

First of all please move all parts creating the response payload into a embed child job to allow testing it without using the webservice.

Indeed multiple responses for one request triggers exactly this exception.