Autosys agent fails to start
search cancel

Autosys agent fails to start


Article ID: 243169


Updated On:


Autosys Workload Automation


Autosys system agent service does not start. The startup command returns "Unable to start agent service"

# ./cybAgent -a
Agent service is starting...
Unable to start Agent service

The file nohup.stderr from the agent install location has the following message - 

# cat nohup.stderr 
Exception in thread "MainThread" java.lang.ExceptionInInitializerError
        at java.lang.J9VMInternals.ensureError(
        at java.lang.J9VMInternals.recordInitializationFailure(
        at java.lang.J9VMInternals.newInstanceImpl(Native Method)
        at java.lang.Class.newInstance(
        at org.bouncycastle.jce.provider.BouncyCastleProvider.loadAlgorithms(Unknown Source)
        at org.bouncycastle.jce.provider.BouncyCastleProvider.setup(Unknown Source)
        at org.bouncycastle.jce.provider.BouncyCastleProvider.access$000(Unknown Source)
        at org.bouncycastle.jce.provider.BouncyCastleProvider$ Source)
        at org.bouncycastle.jce.provider.BouncyCastleProvider.<init>(Unknown Source)
        at java.lang.J9VMInternals.newInstanceImpl(Native Method)
        at java.lang.Class.newInstance(
        at Source)
        at Source)
        at<init>(Unknown Source)
        at<init>(Unknown Source)
        at$a.<clinit>(Unknown Source)
        at Source)
        at Source)
        at cybermation.agent.CybAgentDriver.runApplication(Unknown Source)
        at cybermation.agent.CybAgentDriver.main(Unknown Source)
Caused by: java.lang.NullPointerException
        at sun.misc.Launcher$AppClassLoader.loadClass(
        at java.lang.ClassLoader.loadClass(
        at org.bouncycastle.jcajce.provider.digest.Blake2b$Mappings.<clinit>(Unknown Source)
        ... 19 more


Release : 12.0 and higher

Component : Workload Automation System Agent


This exception is due to the JVM does not have enough heap memory to load all the required java libraries into the process


The default heap size for java is determined based on the available physical memory on the server. And it varies from server to server as the available memory. This problem only appears if the server's available memory is less and, the JVM considers even lesser as a max limit. That might not be enough to load all the required libraries for the applications to function appropriately.

Increase the JVM heap limit for the system agent to 2048m or higher.

Update the following agent property in the agent configuration file (agentparm.txt) -


Restart the agent

Additional Information

Out of Heap exception in autosys system agents -

Default max heap size for Java 8