Getting time out errors when editing conditions

Document ID : KB000090309
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Getting time out errors when editing conditions
Resolution:
Detailed Description and Symptoms

?If you are trying to edit a condition or delete one on a Job/Process Flow where there are a lot of conditions present (usually 100 or more) you may receive a time out error.

You'll see an error similar to the following in the RmiServer<timestamp>.log:

15:40:53.308 thm: null ErrorMsg: AwE-9999 Internal error (5/23/12 3:40 PM)
Details: worker has been running for 123060 ms
 
It is not recommend to have this many conditions on one object.  If you need to edit or remove conditions you may try the "temporary fix" option below.

Solution

?Support should further investigate this issue to determine root cause. 

Go to Help>About Applications Manager>Debug and check "Server"

Try to edit the chain and reproduce the error.

After the error is thrown, open a ticket and attach the latest RmiServer<timestamp>.log file from the Master's $AW_HOME/log directory.


**As a temporary fix: 

Add the following to the [default] section of the Master's $AW_HOME/site/awenv.ini:


ResponseTimeout=180
read_timeout=180

Restart the instance and see if this has an affect. We have had to change the setting to as high as 600 to get this to work but we don't recommend going any higher. We also recommend that once the change is made that the timeouts are removed as they could cause issue down the line if left in place. Sending logs to support is the preferred fix to help determine root cause to the issue.