Esko Logo Back to Esko Support
Choose your language for a machine translation:
Skip to end of metadata
Go to start of metadata



For a couple hours after rebooting the Application Server; after completing a WebCenter task, within a workflow, the next task will not start. The WebCenter JBoss service is showing high CPU usage during this time. After a couple of hours, WebCenter performance is as expected.

What would cause such slow performance after a reboot?


If you have a large number of uncompleted tasks with workflows, it can take a longer time than normal to start all of the workflows, causing slow performance in WebCenter. New workflow tasks will end up at the end of the queue, which means it could take a while for new workflows to get launched.

Check to see how many workflows you have running within WebCenter by doing a search in WebCenter for all tasks in progress. In the resulting search you will see what tasks have workflows attached to them.

Article information
Applies to

WebCenter 12.x

Last revised 
CW Number254467