Skip to main content

"failed to acervate self" error while importing the configuration in 12.x version

Botond Bajka
  • Updated

Overview

While upgrading to version 12.x of Aurea Monitor Management Server you have exported the configuration from 10.x version of AMS and trying to import it in version 12.x.

The Import fails with the below error. The configuration mentioned in the exception is already present.

CFGMGR0022: BaseData '0a239818-buh3xba5c-26e8 (MsgFieldEvaluatorLC) SystemName': failed to acervate self

The full exception is:

CFGMGR0022: BaseData '0a239818-buh3xba5c-26e8 (MsgFieldEvaluatorLC) SystemName': failed to acervate self 
        at com.actional.config.BaseData.acervate(BaseData.java:999) 
        at com.actional.config.BaseData.get(BaseData.java:1071) 
        at com.actional.soapstation.db.LoadableClass.getClassSettings(LoadableClass.java:124) 
        at com.actional.converter.PluginConverter.processMsgFieldEvaluatorLC(PluginConverter.java:59) 
        at com.actional.converter.PluginConverter.processJavaPluginLC(PluginConverter.java:51) 
        at com.actional.converter.PluginConverter.convert(PluginConverter.java:133) 
        at com.actional.config.ConfigReader.executeConverter(ConfigReader.java:554) 
        at com.actional.config.ConfigReader.parse(ConfigReader.java:654) 
        at com.actional.config.ConfigReader.parse(ConfigReader.java:541) 
        at com.actional.task.busdel.DeployZipReader.readFile(DeployZipReader.java:239) 
        at com.actional.task.busdel.DeploymentDelegate.readFile(DeploymentDelegate.java:1287) 
        at com.actional.task.busdel.DeploymentDelegate.readDeploymentFiles(DeploymentDelegate.java:913) 
        at com.actional.task.busdel.DeploymentDelegate.importCustom(DeploymentDelegate.java:746) 
        at com.actional.lg.server.busdel.LGDeploymentDelegate.importCustom(LGDeploymentDelegate.java:621) 
        at com.actional.soapstation.task.DeploymentTask.importCustom(DeploymentTask.java:127) 
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
        at java.lang.reflect.Method.invoke(Method.java:498) 
        at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:735) 
        at com.actional.AuditSessionProxy.invoke(AuditSessionProxy.java:67) 
        at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:729) 
        at com.actional.LogExceptionSession$Proxy.invoke(LogExceptionSession.java:142) 
        at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:729) 
        at com.actional.AsyncCallSession$Proxy.invoke(AsyncCallSession.java:94) 
        at com.actional.APISessionFacade$Handler.invoke(APIFactory.java:747) 
        at com.sun.proxy.$Proxy20.importCustom(Unknown Source)

 

Solution

This issue happens when the custom message field evaluation is used with policy configuration. It first tries to import the message field which cannot find the custom message field plugins, hence the error.

Follow the below steps to resolve the problem:

  1. Export your configuration from version 10.x in two parts:
    1. first export the custom plug-in configuration (the custom message field evaluators) in a separate deploy XML (ex: Deploy_Plugins.xml)
    2. second, export the rest of your configuration items, like policy groups and message fields in a second separate configuration XML (ex: Deploy_All.xml).
  2. When importing your configuration in version 12.x, import them in two parts:
    1. First, import the plug-ins configuration XML (Deploy_Plugins.xml)
      1. Navigate to Deployment -> Import
      2. Click on Deployment File and select your Deploy_Plugin.xml
      3. Enable Activate imported Policy Group revisions and then
      4. Click on the Import button on top.
      5. After successful import, you will notice that the plugins are created under Platform -> Plug-ins.
    2. Second, import the configuration XML file that contains the rest of the artifacts (Deploy_All.xml) by repeating the steps above. After successful import, you will notice that all the message fields and policy groups are imported.

 

Back to the top