Java error on "Execute JavaScript code" action post upgrade to 6.5

Document ID : KB000007991
Last Modified Date : 14/02/2018
Show Technical Document Details

Upgrade of system from 5.5.2 -> 6.1 -> 6.5 resulting in failure of action "Execute Javascript code" with below error

2017-08-25 14:14:58,903 [job-9830408-jobServer-9830408-6:Copy of JS - recuperer la version de Build dans le RM(P16375927.F16375931.E16375932):Execute JavaScript code] ERROR (com.nolio.platform.shared.datamodel.Action:119) - Unexpected failure:java.lang.RuntimeException: java.lang.NoSuchMethodException: None of the fixed arity signatures [(java.lang.Class, int), (java.lang.Class, int[])] or the variable arity signatures [(java.lang.Class, int...)
] of the method java.lang.reflect.Array.newInstance match the argument types [jdk.internal.dynalink.beans.StaticClass, java.lang.Integer]
at jdk.nashorn.internal.runtime.ScriptRuntime.apply(

Release Automation 6.5

During analysis we found that one of the action pack post upgrade on NAC actionslib folder is still of version 6.1. In this case it is the action pack nolio-actions-6.1.0.jar which is defining the action "Execute Javascript code".

As there is a definition change in this jar is not able to match the signature and hence resulting in the error during execution of action "Execute Javascript code".

Error Screen shot:


Note: No nolio-*.jar should be of version 6.1 on system which is upgraded to 6.5 post successful upgrade.

Please follow below step to correct the same

  1. Create a back up of all nolio-*-6.1.0.jar files in actionslib directory on NAC somewhere outside RA install directory
  2. Check for appropriate nolio-*-6.5.0.jars on NAC for example at path webapps/datamanagement/WEB-INF/lib/ and copy the respective jar to client machine used to access Release Operation Center aka ROC. For example in this case the relevant jar was nolio-actions-6.5.0.jar
  3. Login to ROC and navigate to Administration -> Action Management -> Installed Packs and try to upload the nolio-actions-6.5.0.jar manually by clicking import from the path where jar copied in step 2