BAD UNSERIALIZE message floods the SOI catalyst.log on the SOI Manager

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

There are many error messages about "BAD UNSERIALIZE" for different SOI alarms written to \CA\SOI\tomcat\logs\catalyst.log on the SOI manager.
Here is one example of such error message:
 
2018-11-06 11:31:50,476 ERROR [JMS VWAGWOSSCP15.wob.vw.vwg] () impl.SessionImpl.logSDODiagnotic(1494) SOI - ****** BAD UNSERIALIZE ******
sheet: 4027A55CF4234E24A2217B8C13A19D5D
sheet contents:
    xmlns:usm-core="http://ns.ca.com/2009/07/usm-core">
  CA:77001
  xxxxxxxxxxxxxxxxxxxx
  SW11
  SW11
  SW11
  ComputerSystem
  Mainframe SOI HeartBeat
  ComputerSystem
  JMS
  Minor
  Minor
  SW11
  noProduct
  postAlert
  77001
  xxxxxxxxxxxxxxxxxx
  1
  kind regards from xx SOIAgent on SW11
  SW11
  SW11
  SW11
  Mainframe SOI HeartBeat
  CA:77001
  xxxxxxxxxxxxxxxxxxx
  kind regards from xx SOIAgent on SW11
  CAcc_ComputerSystem
  7de6d2e9-8f5f-480e-b278-1cd63ba74a31
  SW11
  noVendor
  SW11
  SW11

XMLHelper instance: [email protected]
XMLHelper instance class: org.apache.tuscany.sdo.helper.XMLHelperImpl
XMLHelper instance class loader: [email protected]
XMLHelper instance class location: file:/D:/CA/SOI/tomcat/lib/tuscany-sdo-impl-1.1.1.jar
 
Can you please explain why this error occurs and how it can be solved? What happens to the data which is (falsely) identified as "Bad Unserialized"?

  

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Cause

there is some error while SOI trying to send notification error message.

it seems , there are some properties are missing for alert or ci while transforming into SOI . if we can configure smtp host then we can get that error.

 

Resolution

We analyzed the warning messages which we are getting in catalyst log file. 

Please configure activemq.xml file as follows.

1. Open activemq.xml file from below path .
\CA\SOI\apache-activemq\conf\activemq.xml

2. Add below highlighted tag inside <policyEntry topic=">" > tag
 <destinationPolicy>
            <policyMap>
              <policyEntries>
                <policyEntry topic=">" >
                    <!-- The constantPendingMessageLimitStrategy is used to prevent
                         slow topic consumers to block producers and affect other consumers
                         by limiting the number of messages that are retained
                        For more information, see:
                        http://activemq.apache.org/slow-consumer-handling.html
                    -->
                  <pendingMessageLimitStrategy>
                   <constantPendingMessageLimitStrategy limit="1000"/>
                  </pendingMessageLimitStrategy> 
                   <deadLetterStrategy>
                      <sharedDeadLetterStrategy processExpired="false"/>     
                    </deadLetterStrategy>     
                </policyEntry>    
              </policyEntries>
            </policyMap>
     </destinationPolicy>
       
3. Restart all the SOI services