Troubleshooting — Unable to synchronize on requestor

Symptom

A user waiting for a response from the Process Commander server receives a window containing the message:

Unable to synchronize on requestor ZZZZZ within 120 seconds.

where ZZZZZ is the requestor ID of the current requestor.

Analysis

This message indicates that the Process Commander server has not responded to a user input for two entire minutes, an unacceptably long interval. The message does not indicate a cause.

The requestor session remains active, but processing of the most recent input is halted and may be incomplete. The following are possible causes:

• The server (processor or memory) is very busy with processing for other users or on tasks and applications not related to Process Commander.
• The server supporting the database is very busy with processing for other users or on unrelated tasks.
• One-time processing at startup — for example extraction and compilation of libraries — has placed a temporary burden on the server.
• Errors have created a looping or compute-bound condition, or a memory-bound condition.
• Errors in database requests have caused it to fail or respond very slowly.
• The processor or database, as currently configured and equipped, is unable to support the current workload.

Action

Resubmit the most recent request. Some conditions causing this error are transient, and may be ignored. If the message recurs, use performance tools to identify and address the performance bottleneck.

Performance checklist

Troubleshooting