Data Collector - "Passed abnormal-service-list-detector checking" error found in karaf.out file

book

Article ID: 223413

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration

Issue/Introduction

The following errors can be displayed in the karaf.out in DC machine:

1-)

=========================
2021-06-23 03:44:20,175 - Passed abnormal-service-list-detector checking. 36 services of org.springframework.context.ApplicationContext found
Exception in thread "ICMPD Response processing executor-thread-1" Exception in thread "ICMPD Response processing executor-thread-2" Exception in thread "ICMPD Response processing executor-thread-3" Exception in thread "ICMPD Response processing executor-thread-4" org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed
 at org.springframework.osgi.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:111)
 at org.springframework.osgi.service.importer.support.internal.support.RetryTemplate.execute(RetryTemplate.java:83)
.
.
.
=========================

OR

 

2-)

=========================
2021-02-09 00:09:35,737 - Passed abnormal-service-list-detector checking. 36 services of org.springframework.context.ApplicationContext found
2021-06-11 12:49:26
Full thread dump OpenJDK 64-Bit Server VM (25.222-b10 mixed mode):
"ActiveMQ Task-3" #4493067 daemon prio=5 os_prio=0 tid=0x00007fe278082800 nid=0x69d6 in Object.wait() [0x00007fe24d507000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
 at java.lang.Object.wait(Native Method)
 at org.apache.activemq.transport.failover.FailoverTransport.doDelay(FailoverTransport.java:1117)
 - locked <0x00000006337ec620> (a java.lang.Object)
 at org.apache.activemq.transport.failover.FailoverTransport.doReconnect(FailoverTransport.java:1106)
 at org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:148)
 - locked <0x00000006337ec608> (a java.lang.Object)
=========================

Cause

The error #1 was generated because the DC was shutting down and ICMP threads were doing something and couldn't complete because the service was destroyed by DC shutting down.

In the error #2, we can see some java stacks dumps being generated. This happened because someone probably did a kill -3 to cause the stacks to dump on the DC.

Environment

Release : 20.2

Component : IM Reporting / Admin / Configuration

Resolution

These errors are not harmful, and can be safely ignored.