Instance times out trying to start but eventually does.

Document ID : KB000087817
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
agentservice.lock file is /tools/apps/mnprd02/status/agentservice.lock
AgentService pid is 12553
waiting for java awapi to start

Error: java awapi timed out.

When trying to start the Application, the process will hang on the following line:
waiting for java awapi to start 

Eventually it will time out with:
Error: java awapi timed out.
 
If trying to log in immediately the application will not launch.

Waiting for a while often allows the application time to start and users can then log in and run jobs. The amount of time to wait is often arbitrary(5 to 30 minutes).
 
Environment:
OS Version: N/A
Cause:
Cause type:
By design
Root Cause: By having large numbers of Jobs in the Backlog with virtual days greater than two days or so back it forces the application to load extra data into memory.
Resolution:
This has been seen when there are greater than two virtual days in the backlog.
Each day requires us to load that days information into memory and can cause issues such as slow startup.

It is recommended to add the virtual day to the backlog as follows:
Options>Tables>Backlog
 
On the screen that pops up check the SO_VIRTUAL_DAY check box and ok out.

This will add the virtual day column to the backlog and allowing it to be sorted by virtual day. 

Delete all jobs out of the backlog older than 2 virtual days.
 

Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A