ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

EM Hangs on Startup with OSGI Message

book

Article ID: 71620

calendar_today

Updated On:

Products

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

Issue/Introduction



  On startup, the Enterprise Manager hangs for an hour or more. The last messages in the log look like this:

org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor timeout
WARNING: Timeout occurred before finding service dependencies for [OsgiBundleXmlApplicationContext(bundle=com.wily.apm.em.monitor.entity.dependency, config=osgibundle:/META-INF/spring/*.xml)]

The EM was working just fine previously.

Environment

  Enterprise Manager (Collector, Stand Alone, or MOM) for all supported releases.

Resolution

  This problem can be caused by corruption of the Traces Database - which stores Transaction Trace data.
To fix this:
  1. Stop the EM
  2. Locate the traces DB folder.  By default, it is in the <EM_HOME>\traces folder, To check look in the IntroscopeEnterpriseManager.properties file for the introscope.enterprisemanager.transactionevents.storage.dir setting - this stores where the traces folder is located.
  3. Rename the traces folder
  4. Restart the EM. It will automatically recreate the traces DB at the same location