Page 1 of 1

Fail to handle multiple web service request with Integrator

Posted: Wed Dec 27, 2017 7:29 pm
by dvanoni
Hi everybody!

I've got a problem with handling multiple REST web service request with Integrator. I created a REST WS with two methods using Integrator. Then I deployed the WS and I configured the Services panel inside Integrator. These WS receive a request from a third-party software and send a response back. Each WS method has its own function component and each function belongs to the same Lansa process. I did these WS following the Lansa documentation and in particular using the HTTPInboundXMLBindService (http://docs.lansa.com/14/en/lansa093/in ... r%7C_____0)

Now if I try the WS using SOAPUI everything works well when I perform a request one after another, i.e. I send a request to the first method, wait for the response from the first method and then I send a request to the second method. In this case if I check the trace files everything is logged and works well. But if I do one request to the first method and one request to the second method almost at the same time, one of the two request fails. If I check the trace files I noticed that the request that fails has the HTTP_CONTENT.XML file empty and then the error in the SERVICE.txt file is "Command : ERROR No document for binding".

Since these WS methods can be potentially called simultaneously, how can I handle multiple WS request correctly? Is it a matter of JSM configuration or what? How can I further investigate the issue?

Thanks for your help

Re: Fail to handle multiple web service request with Integrator

Posted: Wed Dec 27, 2017 8:47 pm
by dvanoni
Just an update: it seems that the request that fails is the first one that Integrator handles as if the second request replaces the content of the first one...
Any advice is appreciated
Thanks

Re: Fail to handle multiple web service request with Integrator

Posted: Thu Jan 25, 2018 5:41 am
by Theo de Bruin
Hello Davide,

Please send your whole Integrator project, as well as the source(s) of your modules ( preferably a Quick Export including all the referenced objects) and some of the trace output from your LANSA Integrator instance jobs to your local support contact.