Summary

What kinds of circumstances can lead to the "Response out of order with previous responses" error?

Question

What kinds of circumstances can lead to the "Response out of order with previous responses" error?

Answer

The reason of the behavior is because FNE server is not built to talk to FNE client more than once per second, it might be returning the same time stamp. The repeating timestamp is the reason for the error.


"Response is out of order with previous responses" refers to FLXERR_RESPONSE_STALE. That happens when you try to apply an old (or same) response to TS. You can generate a request to find what the last response time is that's stored in TS. Compare that against the response time of the capability response you are trying to process, which has to be greater or else you will get the error:

Additional Information

There's no way to bypass this validation, but please consider it as more of a warning that an error and generally can be safely ignored. Look at those errors as the server equivalent to an exasperated parental response to the oft repeated question from their child of "Are we there yet?".

There's little reason to ask for an update to your license rights more than once a second as the expiry of those license rights will be on a second boundary. If you're attempting some kind of load test, you might do better to simulate more than one client. Please note, if you had more than one process sharing the same TS, you also might conceivably get that error.

It's not so much if the requests are different, what's important is either having 1 second between responses OR having the different request/response pairs be for different Host ID/Trusted Storage files. Certainly if the requests come from different systems then you should not see this error as long as each system is keeping a nice pause between requests,

Examples: (Each pair is run on the same physical system.)