Overview

While performing the restarts of Aurea Monitor (Actional) Intermediary (AI) and Aurea Monitor Management Server (AMS) after the installation of jdk1.8 in the Actional servers you are getting errors.

After the JDK 1.8 installation, you changed the JDK reference in env.sh file to /usr/bin/java for 'ACTIONAL_HOME' parameter.
After doing this, while we performing the restarts you are getting below output:

-sh-4.1$ service intermediary stop
Current Java version not supported by ActEndme: /usr/bin/java

Stopping dry7-int-ci1-1
....................Unable to stop dry7-int-ci1-1 after 20 secs!!!

You also have a postcustom.sh file that has been referred in the env.sh file.

Solution

Your postcustom.sh file looks something like this:

if [[ -z `$ACTIONAL_JAVA -version 2>&1 |grep version |awk '{print $3}' | egrep '1.6|1.7'` ]]; then
     echo "Current Java version not supported by ActEndme: $ACTIONAL_JAVA"
else
     export SPACE=" "
     actional_append_java_opts "-XX:OnOutOfMemoryError=/usr/local/tools/Actional/ActEndme/endme.sh\${SPACE}%p"
fi

The error you are receiving is a custom error message generated by your custom script file postcustom.sh, because you (or your internal development team) built into it a logic to accept only JDK version 1.6 or 1.7 (notice the egrep params). This might be due to the fact that you might be using other services on the same server which might not have been certified with JDK 1.8, hence the additional protection in your postcustom.sh file.

The solution is to talk with the team who implemented this postcustom.sh script and ask them to change it to also accept version 1.8 as parameter.

Back to the top