search cancel

Enterprise Dashboard not starting after an upgrade in-place - java.lang.ExceptionInInitializerError


Article ID: 129728


Updated On:


CA Application Test CA Continuous Application Insight (PathFinder)


We upgraded in-place our environment.

We were able to start Identity Access Manager (IAM) successfully. However when starting the Enterprise Dashboard we are seeing the following error:

        at org.codehaus.groovy.runtime.InvokerHelper.<clinit>(
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallStaticSite(
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(
        at dradis.Application.<clinit>(Application.groovy)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
        at com.install4j.runtime.launcher.UnixLauncher.main(Unknown Source)
Caused by: groovy.lang.GroovyRuntimeException: Conflicting module versions. Module [groovy-sql is loaded in version 2.4.4 and you are trying to load version 2.4.7
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl$DefaultModuleListener.onModule(
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromProperties(
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanExtensionModuleFromMetaInf(
        at org.codehaus.groovy.runtime.m12n.ExtensionModuleScanner.scanClasspathModules(
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(
        at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.<init>(
        at groovy.lang.GroovySystem.<clinit>(
        ... 13 more


For some reason the in-place upgrade did not uninstall all the previous files from the environment.

Under $DEVTEST_HOME/lib/dradis folder, it was verified there were several jar files from the previous DevTest version. There were two versions of the same file.

The permissions on these files were different and the installed was unable to remove the previous files.


All supported DevTest releases and platforms.


A new installation of DevTest is required. 

Since the installer was not able to remove the previous files, do the new install on a new directory.

If the same folder structure needs to be used, rename the current installation folder. Example, from /opt/CA/DevTest to /opt/CA/DevTest_backup.

Create a new DevTest folder. Example /opt/CA/DevTest/

Install the product on this new DevTest folder.

After the installation, start DevTest components out of the box to make sure it is working fine.

Then copy the properties files and configure the components with the external database. 

Restart DevTest components.

As a reminder, when using the same database schema the user configured with DevTest needs to have DBA privileges to update the tables.

After the first start and database update, the DBA privileges can be removed.


Additional Information

More information regarding DevTest upgrade in the links below:
Preparing Your DevTest Upgrade -
DevTest Solutions Upgrade Center -