Direct links to fixes
8.1.0-TIV-NCOMNIbus-ZLinux-FP0030
8.1.0-TIV-NCOMNIbus-Windows-FP0030
8.1.0-TIV-NCOMNIbus-Linux-FP0030
8.1.0-TIV-NCOMNIbus-AIX-FP0030
8.1.0-TIV-NCOMNIbus-ZLinux-FP0029
8.1.0-TIV-NCOMNIbus-Windows-FP0029
8.1.0-TIV-NCOMNIbus-Linux-FP0029
8.1.0-TIV-NCOMNIbus-AIX-FP0029
8.1.0-TIV-NCOMNIbus-ZLinux-FP0028
8.1.0-TIV-NCOMNIbus-Windows-FP0028
8.1.0-TIV-NCOMNIbus-Linux-FP0028
8.1.0-TIV-NCOMNIbus-AIX-FP0028
8.1.0-TIV-NCOMNIbus-ZLinux-FP0026
8.1.0-TIV-NCOMNIbus-Windows-FP0026
8.1.0-TIV-NCOMNIbus-Linux-FP0026
8.1.0-TIV-NCOMNIbus-AIX-FP0026
8.1.0-TIV-NCOMNIbus-ZLinux-FP0024
8.1.0-TIV-NCOMNIbus-Windows-FP0024
8.1.0-TIV-NCOMNIbus-Linux-FP0024
8.1.0-TIV-NCOMNIbus-AIX-FP0024
8.1.0-TIV-NCOMNIbus-ZLinux-FP0023
8.1.0-TIV-NCOMNIbus-Windows-FP0023
8.1.0-TIV-NCOMNIbus-Linux-FP0023
8.1.0-TIV-NCOMNIbus-AIX-FP0023
8.1.0-TIV-NCOMNIbus-ZLinux-FP0022
8.1.0-TIV-NCOMNIbus-Windows-FP0022
8.1.0-TIV-NCOMNIbus-Linux-FP0022
8.1.0-TIV-NCOMNIbus-AIX-FP0022
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 22, 8.1.0-TIV-NCOMNIbus-FP0022
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 23, 8.1.0-TIV-NCOMNIbus-FP0023
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 24, 8.1.0-TIV-NCOMNIbus-FP0024
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 26, 8.1.0-TIV-NCOMNIbus-FP0026
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 25, 8.1.0-TIV-NCOMNIbus-FP0025
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 27, 8.1.0-TIV-NCOMNIbus-FP0027
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 28, 8.1.0-TIV-NCOMNIbus-FP0028
Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 29, 8.1.0-TIV-NCOMNIbus-FP0029
APAR status
Closed as program error.
Error description
L3 analyzed the symtom and provided the comment below. "Based on the fact that shutting down PA with the "-option STOP" will also stop managed processes, and based on the location of the thread in the core (sending a GW watch to the ObjectServer) I suspect the ObjectServer has exited before the gateway had a chance to send its GW watch, and the connection was marked dead but not handled correctly in doing so, resulting in the crash. Based on the code, it looks like the session being used is garbage, so the pointers being used are invalid. This will be the result of the session being de-allocated and the memory reused, and so filled with garbage as far as session data is concerned. It is noted in the code that a GW watch is being sent when the backup ObjectServer connection is lost, but with no primary connection to send it to (which is also lost) the result is this crash. This is definitely a bug, but the consequences are minimal in the circumstances, as it appears everything is being shut down anyway."
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of the OMNIbus bidirectional gateway * **************************************************************** * PROBLEM DESCRIPTION: * * On shutdown of the gateway, the gateway could crash while * * attempting to send a gateway watch event. Alternatively, the * * gateway could change the ActingPrimary of the backup * * ObjectServer, resulting in resync problems upon restart. * **************************************************************** * RECOMMENDATION: * * Apply the maintenance vehicles listed in the Problem * * Conclusion. * ****************************************************************
Problem conclusion
The fix for this APAR is contained in the following maintenance packages: | fix pack | 8.1.0-TIV-NCOMNIbus-FP0022
Temporary fix
Comments
APAR Information
APAR number
IJ02708
Reported component name
NC/OMNI GTWY (B
Reported component ID
5724O73OS
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-17
Closed date
2019-11-27
Last modified date
2019-11-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
NC/OMNI GTWY (B
Fixed component ID
5724O73OS
Applicable component levels
Document Information
Modified date:
17 March 2023