Spectrum SRM - DOES_NOT_EXIST exception occurs while retrieving events for <landscape_name>
search cancel

Spectrum SRM - DOES_NOT_EXIST exception occurs while retrieving events for <landscape_name>

book

Article ID: 138533

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

In the Spectrum Tomcat logs, the following error relating to Spectrum Report Manager (SRM) is generated:

Oct 11, 2019 07:13:54.881 (SRM/EventPoller/<landscape_name>) (SRM_Events) - (ERROR) - Expection occurs while retrieving events for <landscape_name>. retrying in cycle

Caused by: exception com.aprisma.spectrum.core.idl.CsCException.CsCSpectrumException {

com.aprisma.spectrum.core.idl.CsCError.CsCError_e error=DOES_NOT_EXIST,

java.lang.String messageFormatID="CsCEventDomain.getNextEventListByAttrFilter.requestID.DOES_NOT_EXIST"

As a result, the events from the related landscape will not be polled/processed by SRM due to the "DOES_NOT_EXIST" CORBA exception.

 

Environment

DX NetOps 20.2 or later Spectrum
Component : Spectrum Report Manager

Cause

SRM logs have bucket files stuck

Resolution

You can force the polling of the events to be done even after this exception, by executing the following procedure:

  1.  On the Spectrum OneClick server with SRM, open the following file:

    $SPECROOT\tomcat\webapps\spectrum\WEB-INF\web.xml 

  2. Locate the following lines:

    <context-param xmlns="">

        <param-name>com.aprisma.spectrum.app.repmgr.dc.event.ForceEventPolling</param-name>

        <param-value>false</param-value>

        <description>

            Enabling Event polling forcefully after CORBA DOES_NOT_EXIST exception

        </description>

    </context-param>

  3. Set the above flag (<param-value>) from "false" to "true";

  4. Restart the tomcat;