APM Enterprise Manager fails to start and gives an "error activating bean" Java exception.

Document ID:  TEC607007
Last Modified Date:  08/02/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Application Performance Management

Releases

  • CA Application Performance Management:Release:9.1 SP2
  • CA Application Performance Management:Release:9.1.0
  • CA Application Performance Management:Release:9.1.1
  • CA Application Performance Management:Release:10.0
  • CA Application Performance Management:Release:10.1
  • CA Application Performance Management:Release:10.2
  • CA Application Performance Management:Release:10.5
  • CA Application Performance Management:Release:10.3
  • CA Application Performance Management:Release:10.5.1
  • CA Application Performance Management:Release:CA APM 9.6
  • CA Application Performance Management:Release:CA APM 9.7

Components

  • INTROSCOPE:APMISP
Problem:

 Introscope Enterprise Manager fails to start. The following error message appears in the IntroscopeEnterpriseManager Log at the DEBUG logging level:

 

[ERROR] [main] [Manager] The EM failed to start. Error activating bean: com.wily.introscope.server.beans.apm.ApmServiceBean (com.wily.introscope.server.beans.apm.ApmServiceBean)
[VERBOSE] [main] [Manager]

com.wily.isengard.container.BeanActivationException: Error activating bean: com.wily.introscope.server.beans.apm.ApmServiceBean (com.wily.introscope.server.beans.apm.ApmServiceBean)
at com.wily.isengard.container.BeanActivator.activateBean(BeanActivator.java:390)
at com.wily.isengard.container.BeanContainerCore.addBean(BeanContainerCore.java:150)
at com.wily.isengard.catalog.server.CatalogCore.addBeanToCatalogAndCore(CatalogCore.java:82)
at com.wily.isengard.catalog.server.CatalogCore.addBean(CatalogCore.java:148)
at com.wily.isengard.catalog.server.CatalogBean.addBean(CatalogBean.java:66)
at com.wily.introscope.server.enterprise.EnterpriseServer$ExtensionBeanDescriptor.deploy(EnterpriseServer.java:2524)
at com.wily.introscope.server.enterprise.EnterpriseServer.startBeans(EnterpriseServer.java:839)
at com.wily.introscope.server.enterprise.EnterpriseServer.loadBeanExtensions(EnterpriseServer.java:811)
at com.wily.introscope.server.enterprise.EnterpriseServer.initialize(EnterpriseServer.java:654)
at com.wily.introscope.server.enterprise.EnterpriseServer.doStart(EnterpriseServer.java:360)
at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:303)
at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:282)
at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1483)
at com.wily.introscope.em.internal.Activator.startEM(Activator.java:116)
at com.wily.introscope.em.internal.Application.start(Application.java:27)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
at org.eclipse.core.launcher.Main.main(Main.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.zerog.lax.LAX.launch(DashoA10*..)
at com.zerog.lax.LAX.main(DashoA10*..)
Caused by: com.wily.introscope.osgi.LocalServiceNotFoundException: Couldn't find local service com.wily.apm.model.IApmDataService
at com.wily.introscope.server.beans.LocalServiceCache.getLocalService(LocalServiceCache.java:105)
at com.wily.introscope.server.beans.ALocalServiceHandle.getLocalService(ALocalServiceHandle.java:65)
at com.wily.introscope.server.beans.AServerBean.getLocalService(AServerBean.java:222)
at com.wily.introscope.server.beans.apm.ApmServiceBean.activate(ApmServiceBean.java:148)
at com.wily.isengard.container.beans.AIsengardBean.doStart(AIsengardBean.java:92)
at com.wily.util.ALifeCycle.start(ALifeCycle.java:86)
at com.wily.isengard.container.BeanActivator.activateBean(BeanActivator.java:365)
... 35 more

Environment:
All supported APM releases.
Cause:

May be a connection problem between EM and the database. (Oracle or Postgres.)

Workaround:

Workaround 1:

 

Implement only if not using the APM database (Postgres or Oracle) and CEM. In addition, do the following if there is no need for AppMap (Triage Map) metrics:

 

  1. Open the IntroscopeEnterpriseManager.properties file in <EM_HOME>/config.
  2. Add below row at the end of the documention:
    introscope.apm.feature.enabled=false
  3. Save the IntroscopeEnterpriseManager.properties file.
  4. Start Introscope Enterprise Manager.

 

Workaround 2:

The issue can also be a password mismatch/forbidden between DB and "tess-db-cfg" from MOM side.

To correct, do the following:

    1.  Erase encrypted password from

-<property name="hibernate.connection.password">ENC(DiYV7NdIz+YTGdYWAZhTCQ==)</property> 

    2.  Write the APM database password as plain text

-<property name="hibernate.connection.password">PASSWORDVALUE</property>

    3.  Change below properties from FALSE to TRUE

-<property name="plainTextPasswords">false</property>

4. Restart the Introscope Enterprise Manager.

Additional Information:

Note: For workaround 1, this is a hidden property which is set to true by default, thus this line must be manually added to the properties file.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >