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"?
Release : 4.2
Component : Service Operations Insight (SOI) Manager