APAR status
Closed as program error.
Error description
MQ appliance might restart unexpectedly while performing SSL connections flows due to SIGSEGV. The backtrace will show following stack #0 0x00007f4eb8b170bd in nanosleep () from /???/libc.so.6 #1 0x00007f4eb8b16f57 in sleep () from /???/libc.so.6 #2 0x0000000000677b62 in _Z25generateExtendedBacktracev () #3 0x000000000067921a in _Z15SaveToBacktraceiP9siginfo_tPvmPKcS3_S3_S3_S3_ ( #4 0x0000000000cf6d18 in PrintBacktraceImpl (signum=signum@entry=11, #5 0x0000000000cf6f67 in default_sig_handler(int, siginfo_t *, void *) ( #6 <signal handler called> #7 0x00007f4ebb234689 in SSL_CIPHER_get_name () from /???/libssl.so.1.0.0 #8 0x0000000000b02610 in _ZN18drMultistepEnabled18ProcessSSLAuthInfoEP5arenaPKcS3_P5drSSL P18drSSLReadWriteInfo (h=0x7f4cd480b008, type=0x300d4f7 "s"..., #9 0x00000000007c0602 in _ZN9drGateway8AuthInfoEP5arenaPKcS3_ ( #10 0x0000000000cc9d87 in _ZN14drSinkProtocol10BaseStreamEv ( #11 0x0000000000cca1b0 in _ZN14drSinkProtocol11DriverSetupEv ( #12 0x00000000007cc024 in _ZN9drGateway15GetBackProtocolEv ( #13 0x00000000007cc3e9 in _ZN9drGateway13NoMoreHeadersEv ( #14 0x00000000007d773d in _ZN9drGateway34Process_State_Front_BackConnectionEv #15 0x00000000007c991c in _ZN9drGateway12ParsePayloadEv (this=0x7f48be950028) #16 0x00000000007bf2c1 in _ZN9drGateway27FrontProcessorEventCompleteEPvS0_ ( #17 0x0000000002716e54 in _ZN12dpDispatcher12ServicePortsEil ( #18 0x000000000271e263 in _ZN12dpDispatcher11SleepOrWorkEi ( #19 0x000000000272b092 in _ZN15dpThreadManager15ThreadEntryProcEPv ( #20 0x0000000002adb202 in start_dpthread (arg=<optimized out>) #21 0x00007f4eb9a52e91 in ??? () from /???/libpthread.so.0 #22 0x00007f4eb8b51cbd in ??? () from /???/libc.so.6
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All MQ appliance users Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: A defect while attempting to log SSL session information caused memory access violation and resulted in appliance reload.
Problem conclusion
MQ appliance code has been modified to perform additional checks to prevent the memory access violation error. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.2 LTS 9.2.0.5 v9.x CD 9.2.1 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT36102
Reported component name
MQ APPL M2002 V
Reported component ID
5737H4701
Reported release
920
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-03-03
Closed date
2021-12-21
Last modified date
2022-02-01
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
MQ APPL M2002 V
Fixed component ID
5737H4701
Applicable component levels
[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920"}]
Document Information
Modified date:
02 February 2022