Use the custom Java class to implement custom error checking.
A custom result checker can throw errors for both a scheduled cache refresh as well as an on demand cache refresh:
- For a scheduled refresh – the result checker writes a log message that describes the nature of the error to the Unwired Server log. As a consequence of this error, the transaction for the entire cache group is rolled back. The device client user is not notified of these errors; no client log records are generated.
- On demand refresh – instead of writing the error to the server log, the log message is written to the Unwired Server. Services in the server handle the exception. As a consequence of this error, the transaction for the cache group is rolled back. But in this case, a client log record is generated, which is visible to the client application after synchronization.
Both cases send the OperationStatusEvent. This event indicates that an operation failed to execute properly. The server uses OperationStatusEvent to populate a statistics repository that tracks the success or failure of EIS operation invocations. An administrator can review these statistics in Sybase Control Center, by clicking the Monitor node in the left navigation pane. See System Administration of the Unwired Platform > System Maintenance and Monitoring > Status and Performance Monitoring > Reviewing System Monitoring Data.