Error messages and problem solving
You might encounter some problems at run time. Use this information to resolve some of these common runtime problems.
Runtime problems and corrective actions are described in the following table.
| Problem | Corrective Action |
|---|---|
Reconciliation does not return all ServiceNow accounts. Reconciliation is successful but some accounts are missing. |
For the adapter to reconcile many accounts successfully,
you might need to increase the WebSphere JVM memory. The complete
the following steps on the WebSphere host computer: Note: Do not increase
the JVM memory to a value higher than the system memory.
If the allocated JVM memory is not large enough, an attempt to reconcile many accounts with the adapter results in log file errors. The reconciliation process fails. The adapter log files contain entries that state ErmPduAddEntry failed. The WebSphere_install_dir/logs/itim.log file contains java.lang.OutOfMemoryError exceptions. |
|
Reconciliation API throws error "Transaction cancelled: maximum execution time exceeded. "This error comes when execution time exceeded. |
By default on instance maximum time duration is 60 sec. whenever any API takes
tore than 60 seconds, it throws "error":{"message":"Transaction cancelled: maximum
execution time exceeded","detail":"Transaction cancelled: maximum
execution time exceeded". Check logs for error trace or enable glide.rest.debug property to verify REST request processing"}. You can increase this execution time on instance, Navigate to . Then search for the name with REST Table API request timeout. Change the maximum duration field's value. |