Spectrum Report Manager SRM stops processing for some SpectroSERVERs
Article ID: 281900
Updated On:
Products
Issue/Introduction
After cycling the OneClick tomcat server hosting the Spectrum Report Manager it was noticed that a couple of the SpectroSERVERs were no longer updating. The catalina.out provided no indication of a problem. It actually showed that the SpectroSERVERs not updating would be reported on.
Mysql was consuming over 200% cpu. When logging into mysql and running show full processlist\G it was noticed that the same SELECT statement was running but the time was not incrementing.
The mysql output shows:
Info: select event_key from event where model_key=12345 and type=78446602 and UNIX_TIMESTAMP(time)=1711218747
and
Info: select event_key from event where model_key=12345 and type=78446599 and UNIX_TIMESTAMP(time)=1711218747
Cause
SRM was stuck processing events for Spectrum Policy Manager.
Resolution
Utilize the SRM event filter to filter out the Policy events
Copy the event-processing-filter.xml and event-processing-filter-schema.xsd files to the 'custom' directory. For example, see the following syntax:
cp <$SPECROOT>/tomcat/webapps/spectrum/WEB-INF/repmgr/config/event-processing-filter-schema.xsd <$SPECROOT>/custom/repmgr/config/
cp <$SPECROOT>/tomcat/webapps/spectrum/WEB-INF/repmgr/config/events/event-processing-filter.xml <$SPECROOT>/custom/repmgr/config/
Edit the event-processing-filter.xml Event 0x10017 and event 0x1030a are Authentication Failure events. Events
<ignore>
<event-type>0x10017</event-type>
<event-type>0x1030a</event-type>
<event-type>0x4ad0000</event-type>
<event-type>0x4ad0001</event-type>
<event-type>0x4ad0002</event-type>
<event-type>0x4ad0003</event-type>
<event-type>0x4ad0004</event-type>
<event-type>0x4ad0005</event-type>
<event-type>0x4ad0006</event-type>
<event-type>0x4ad0007</event-type>
<event-type>0x4ad0008</event-type>
<event-type>0x4ad0009</event-type>
<event-type>0x4ad000a</event-type>
<event-type>0x4ad000b</event-type>
<model></model>
</ignore>
Feedback
