Workflow (JobP) takes long time to start after activation

Document ID : KB000092820
Last Modified Date : 02/05/2018
Show Technical Document Details
Issue:
1. Issue:
  •  Workflow (JobP) takes long time to start after being activated by schedule object
  • Ex: JobP's active time was 4:45 AM, but JobP's start time delayed for long time, it might be 8:30 AM or later.
2. What the log shows in this case:
  • In the log file can see something similar to this
User-added image
  • Between JobP active event and JobP start event, there might be many warning message
                - DB table 'MQ1WP' needs to be reorganized. This will be done as soon as possible.
       and it does not have messages:
                - ​DB table 'MQ1WP' is going to be reorganized ...
                - DB table 'MQ1WP' was reorganized.

 
Cause:
System workload high at the time JobP activated
  • The MQ table was full at the time JobP activated, system attempted to reorg the MQ table many time with no success so that system consider the MQ table still full and do not allow JobP to join the Queue to start.
  • JobP has to wait until the system successfully active the MQ reorg function and put it in the queue
Resolution:
1. Workaround:
  • Turn off the Automic MQ reorg function in your system. This can be done by add a new static values to UC_SYSTEM_SETTINGS name AUTOMATIC_MQ_REORG with value 1=N.
2. Resolution:
  • Optimize the system workload