Applications Manager's "java awapi timed out" error message

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When starting Applications Manager, processes may fail to start and the error message "java awapi timed out" may appear.

This error is a general error message that occurs anytime the RmiServer and/or AgentService processes fail to start within 90 seconds.

To determine why the RmiServer and/or AgentService processes did not start, a review of the RmiServer logs and AgentService logs generated at time of startup is required.

An "AwE-" or "ORA-" error is likely thrown in one of the log files generated in the $AW_HOME/log directory.

If no errors are found or if found errors does not help resolve the issue, open a case with Broadcom Support after enabling debug, restarting Applications Manager, and gathering logs.

Debug and log information found in Resolution section

 

 

Resolution

Enable debug by editing the $AW_HOME/site/awenv.ini file and adding the line "debug=true" in the second line of the file, just under the line "[default]". The debug line can be anywhere as long as it is in the [default] section. Save file.

Restart Applications Manager processes and allow the java awapi to time out.

Open a case with Broadcom Support for the error, any additional information surrounding the issue, and upload the following files to the case.

RmiServer.log
RmiServer<timestamp>.log (should be the first timestamp log generated after the RmiServer.log.  If the RmiServer process fails to start, this file may not be available)
AgentService.log
AgentService<timestamp>.log (should be the first timestamp log generated after the AgentService.log. If the AgentService process fails to start, this file may not be available)