search cancel

Enterprise Manager collector LogServiceActivator.start() of bundle com.wily.osgi.logservice

book

Article ID: 242274

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Upgraded the JDK/JRE from 1.8.0.322 to 1.8.0.332 and on one of Ten collectors received the below error on startup:

The other nine collectors in the APM cluster had no such error.

 

------------------ error in the IntroscopeEnterpriseManager.log -------------

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

!ENTRY org.eclipse.osgi 4 0 2022-05-23 07:31:40.701
!MESSAGE An error occurred while automatically activating bundle com.wily.osgi.logservice (106).
!STACK 0
org.osgi.framework.BundleException: Exception in com.wily.osgi.service.log.internal.LogServiceActivator.start() of bundle com.wily.osgi.logservice.
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1028)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
        at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
        at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:368)
        at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:33)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:441)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:397)
        at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:385)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:87)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at com.wily.introscope.osgi.ABundleActivator.start(ABundleActivator.java:55)
        at com.wily.introscope.client.internal.ClientActivator.start(ClientActivator.java:48)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:265)
        at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
        at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
        at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:427)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:193)
        at org.eclipse.osgi.framework.internal.core.BundleLoader../EMCtrl.sh stop: Enterprise Manager stopped
Debug options:
    file:/tmp/.options not found
log4j:WARN No appenders could be found for logger (org.springframework.osgi.extender.internal.activator.ContextLoaderListener).
log4j:WARN Please initialize the log4j system properly.

 

Environment

Release : 10.7.0

Component :

Resolution

Stopped the enterprise manager, cleared the tmp | product\enterprisemanager\configuration caches, then started the EM.

Started without any errors.