API Call: Not always a Response

[René Houba]

Hi,

I have this situation:
A JDEdwards environment activated a LANSA API. This works fine.
In the LANSA Server Module that is activated I call a function to do all kind of I/O's and in the end, when all is done properly, I activate a Reusable Part (#PRIM_OBJT) to call/activate a JDEdwards API. The only thing that this call is doing is telling JDE that the activities is LANSA are done.

The environment is completely Windows (LANSA V15 with the latest EPC's), including the LANSA Webserver environment in Windows via IIS (running on the same Windows server).

The problem we have is:
Most of the time, the call to the JDE API is successful. I generate HTTP logging and see that I send out a Request and receive a Response:

JDE API call with Response.JPG (26.92 KiB) Viewed 46511 times

But in some situations, we do not get a Response:

JDE API call without Response.JPG (23.51 KiB) Viewed 46511 times

But if we activate the same situation for example some minutes later, all is ok and we get a response.

In the situation were we do not get a response, we do not see for example any activity in the firewall that shows that we do the call and/or get the reponse.

Does anyone have had a siutation like this?
Or a tip to get some extra logging, so more then the http logging that I already create?

Kind regards,
René

[Dino]

I noticed that kind of issue when added a windows machine in the middle and that windows machine was in an azure cloud instead of locally in our network. Seems that the windows machine goes to sleep after a while and the call to the service when this happens, returns no response but the next call gets a response, so kind like the first calls after it went to sleep wakes the machine up.

I'm not expert in windows but the expert in that has been looking everywhere for settings in the windows machine that make the machine to sleep, no success finding it yet.

You can plan for these, like retry, or have a process in that windows machine to try to keep it awake

[René Houba]

Hi Dino,

Thanks for your reply.

I already built in, if the API CALL fails, that I try this again (max 5 times with inbetween an OV_SLEEP of 10 seconds), but so far they all fail.

So as you suggested, we have to find where it fails in the windows layer.....