App-C is expecting the user’s laptop that runs CDT to be time-synchronized with the App-C backend. The workaround is to reset the System Time on the laptop, which of course is not optimal.

Scenario: Use CDT to try to perform a ConfigModify.

Attached is a screenshot of the INPUT and RESPONSE.  You see in the response that we get an error message about invalid input parameter and the “Timestamp is of future” error from CDT. We tried a lot of different things after checking the karaf.log, and it turns out that the basic problem is that App-C CDT is comparing

• the timestamp of the incoming request, with the user’s laptop timestamp, with
• the timestamp of the server where the App-C/CDT code is running.

If the user’s laptop happens to have a different SYSTEM TIME than the CDT server, where the system time in CDT backend is behind that of the laptop, CDT fails with the message about "Timestamp is of future".

We confirmed this by setting the user laptop SYSTEM TIME one minute behind, and then we don’t see this error from CDT.