Java Version match on Master and agent
search cancel

Java Version match on Master and agent


Article ID: 226940


Updated On:


CA Automic Applications Manager (AM)


Do we need to use matching java versions on master and remote agent?

Our master is currently using openjdk version "11.0.10" 2021-01-19 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.10+9-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.10+9-LTS, mixed mode, sharing)

However, the remote agent is running the following:

java -version
openjdk version "1.8.0_282"
OpenJDK Runtime Environment (build 1.8.0_282-b08)
OpenJDK 64-Bit Server VM (build 25.282-b08, mixed mode)


CA Automic Applications Manager 9.3x


Mismatch of java version on agent and master.


There is no requirement for matching version of type and java on the master / remote agent and you should be able to use any compatible version of java per our compatibility matrix found here:

However, it is highly recommended to use the same version and type of java on master/agent because Java can easily make a change in the newer java version which breaks the AM connection if the master is using the new version and the agent is not.

Additional Information

A good example scenario would be the one described in the KB below:

The KE talks about how Java 8 update 201 changes can break the connection if one component if running equal or greater than 201 and the other is running less then 201.