The EM failed to start. Error activating bean.
search cancel

The EM failed to start. Error activating bean.

book

Article ID: 196735

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

Tried installing APM 10.7 GA.

EM is not able to start - get the below errors on the IntroscopeEnterpriseManager.log

[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)
--
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)

 

Environment

  • Release : APM 10.7.0
  • JDK: Open JDK 1.8
  • OS: Red Hat Enterprise Linux Server release 7.8 (Maipo)
  • Component : APPLICATION PERFORMANCE MANAGEMENT

Cause

  • Caused by not being able to initiate the OpenJDK - seems like it is related to permissions. 

Resolution

EM started after changed to the default EM jdk from OpenJDK  in the IntroscopeEnterpriseManager.lax

lax.nl.current.vm=

#   LAX.NL.CURRENT.VM
#   -----------------
#   the VM to use for the next launch

lax.nl.current.vm=/opt/ca/jdk/jre/bin/java

If this is a Windows server and you are running the Enterprise Manager as a service you will need to modify the EMService.conf file.  It can be found in the <EM Home>\bin folder.

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
#  Locate the java binary on the system PATH:
wrapper.java.command=jre\\bin\\java.exe

ex. wrapper.java.command=C:\\Program Files\\Java\\jdk1.8.0_281\\jre\\bin\\java.exe

Additional Information

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