DX-APM-10.7 HF# 84 EM - fails to start after
search cancel

DX-APM-10.7 HF# 84 EM - fails to start after

book

Article ID: 242010

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

After applying Hot fix 84 to APM 10.7 fresh install 10.45, the EM fails to start due to an exception.

 

Command-line arguments:  -consolelog -product com.wily.introscope.em.product

 

!ENTRY org.eclipse.osgi 

!MESSAGE Bundle [email protected] not found.

log4j:ERROR Could not instantiate class [com.wily.apm.tess.supportability.TessPerformanceLogFileAppender].

java.lang.ClassNotFoundException: com.wily.apm.tess.supportability.TessPerformanceLogFileAppender cannot be found by com.wily.log4j_1.2.17

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)

at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)

at java.lang.ClassLoader.loadClass(ClassLoader.java:351)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:264)

at com.wily.org.apache.log4j.helpers.Loader.loadClass(Loader.java:198)

at com.wily.org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:327)

at com.wily.org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:124)

at com.wily.org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:785)

at com.wily.org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)

at com.wily.org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)

at com.wily.org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)

at com.wily.org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:440)

at com.wily.util.feedback.backend.log4j.Log4JBackend.configureFromProperties(Log4JBackend.java:97)

at com.wily.introscope.server.enterprise.entity.prefs.Log4jConfigUpdater.<init>(Log4jConfigUpdater.java:51)

at com.wily.introscope.server.enterprise.entity.prefs.PreferencesEntity.finishStartup(PreferencesEntity.java:312)

at com.wily.introscope.server.enterprise.EnterpriseServer.finishStartup(EnterpriseServer.java:1046)

at com.wily.introscope.etc.AIntroscopeInstalledApplication.<init>(AIntroscopeInstalledApplication.java:79)

at com.wily.introscope.etc.AIntroscopeInstalledApplication.<init>(AIntroscopeInstalledApplication.java:52)

at com.wily.introscope.etc.AIntroscopeLicensedApplication.<init>(AIntroscopeLicensedApplication.java:63)

at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:325)

at com.wily.introscope.server.enterprise.EnterpriseServer.<init>(EnterpriseServer.java:309)

at com.wily.introscope.server.enterprise.EnterpriseServer.start(EnterpriseServer.java:1614)

at com.wily.introscope.em.internal.Activator.startEM(Activator.java:119)

at com.wily.introscope.em.internal.Application.start(Application.java:27)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)

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 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(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.zerog.lax.LAX.launch(Unknown Source)

at com.zerog.lax.LAX.main(Unknown Source)

log4j:ERROR Could not instantiate appender named "tessperformance".

[INFO] [main] [Manager] Introscope Enterprise Manager Release 10.7.0.358 (Build 998412)

 

Steps Taken:

      1. PostgreSQL installed as non-root
      2. New EM 10.7 build 45 installed  as non-root
      1. Verified working
      2. Shutdown PG and EM
      3. Applied HF84 to PG successfully
      4. Applied HF84 to EM successfully
      5. Started PG
      6. Started EM and failed
      7. Shutdown EM
      8. Remove EM directory
      9. Installed EM  45
      10. Installed HF84
      11. Started EM and failed same as before.

 

 

Environment

Release : 10.7.0

Component : Introscope

Cause

CEM Properties 

Resolution

Update the  IntroscopeEnterpriseManager.properties file and comment out the TESS logging properties 

### Logging for Tess performance log ###
#log4j.additivity.com.wily.apm.tess.supportability.TessPerformanceCollector=false
#log4j.logger.com.wily.apm.tess.supportability.TessPerformanceCollector=INFO, tessperformance
#log4j.appender.tessperformance=com.wily.apm.tess.supportability.TessPerformanceLogFileAppender
#log4j.appender.tessperformance.layout=com.wily.org.apache.log4j.PatternLayout
#log4j.appender.tessperformance.layout.ConversionPattern=%d{M/dd/yy hh:mm:ss a z},%m%n
#log4j.appender.tessperformance.File=logs/tessperflog.txt
#log4j.appender.tessperformance.MaxSize=4000000

Powered by Wolken Software