Agent does not start. It exits with message "System.exit(99) has been invoked".

book

Article ID: 51226

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent CA Workload Automation Agents DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Description:

When trying to start the agent, it exits with "System.exit(99) has been invoked" in runner_os_component.log. No other log file is created.

The runner_os_component.log

Solution:

The "System.exit(99) has been invoked'" is most probably because of the unrecognized parameters in the agentparm.txt.

Under 'Additional Jars' in the agentparm.txt, the following parameter may wrap at the end of the line to a new line:

"oscomponent.classpath=jars/core.jar:jars/filemon.jar:jars/ftp.jar:jars/gnu.zip:jars/library.jar:jars/management.jar:jars/objmon.jar:jars/pluginlib.jar:jars/
regex.jar:jars/router.jar:jars/runner.jar:jars/snmp.jar:jars/utility.jar:jars/alchemist.jar:jars/tcpip.jar:jars/filebrowser.jar:jars/config.jar:jars/ext/*:jars/js.jar:jars/ps.jar"

It's possible that some editors may save the lines with a carriage return and result in breaking the classpath and introduce unknown parameters.

To fix this, open the agentparm.txt in vi (UNIX/Linux) or Notepad (Windows). Join the lines; make sure that the classpath includes all the jars.

Save the agentparm.txt and start the agent.

Note: Make sure Word Wrap under Format is not turned in Notepad.

Environment

Release: CAWAS999000-11.1-Workload Automation-Agent for Application Services
Component: