Asynchronous Data Validation Troubleshooting Overview

Answer

Starting in Maximo Asset Management 7.5.0.1, Maximo can validate data asynchronously. This means that a user can enter data and proceed to the next action before validation is done. If the data is found to be invalid, you will eventually see a red x icon showing that the value entered is not valid.

Each validation request sent from the client has a sequence number associated with it. More than one event can be sent to the server at the same time. Given the nature of TCP/IP (network packets are sent continuously without requiring acknowledgment it has been received), you are not guaranteed that the first request sent from the client will be the first one to reach the server.

Therefore, if an request is received out of order, the Maximo framework will wait (by default) twenty seconds for the earlier sequenced request to reach the server. If the earlier sequenced events(s) have not "come in" after twenty seconds, the Maximo framework will send the error message to the client's browser,

This can happen for a number of reasons. One way is that a request sent from the client (browser) never made it to the application framework. This could be caused by a network "hiccup", a server error, or, potentially, a bug somewhere in Maximo.

After this happens, the user reloads the application by clicking on the Reload button. However, they could have lost data, and they may have to redo the last few events.

Example 1: The user types a value into a field, then clicks on the Save button. They receive the error message. After reloading, the user may have to reenter that value and hit the Save button again.

Example 2: The user is doing something basic, such as change tabs. They receive the error message. After reloading, all they would need to do is click the tab again. In this case data probably isn't lost.

This message should be rarely seen if at all. If users see this message frequently, then besides network issues, the System Property mxe.webclient.outOfOrderReqTimeout might be set too low. You can reset the default value or specify a higher value.