APAR status
Closed as program error.
Error description
While adding charts using the IBM MQ V9.1 Console (WebUI), the following failure data capture (FDC) pattern was generated: . First an FDC, containing only the date and time, was created, followed by the following FDCs ZX065030 zxcInitiator amqzxma0 zrcC_E_INVALID_HANDLE ZX061015 zxcSelectSocketAgent amqzxma0 xecP_E_INVALID_PID XC130004 xehExceptionHandler amqzlsa0 STOP SIGSEGV ZL107060 zlsMainThread amqzlsa0 xecF_E_UNEXPECTED_RC The relevant stack from the SEGV FDC is: | Probe Id :- XC130004 | | Component :- xehExceptionHandler | | Program Name :- amqzlsa0 | O/S Call Stack for current thread /opt/mqm/lib64/libmqmcs_r.so(+0xffc3e)[0x7f1b5b949c3e] /opt/mqm/lib64/libmqmcs_r.so(+0x120f8a)[0x7f1b5b96af8a] /opt/mqm/lib64/libmqmcs_r.so(+0x120668)[0x7f1b5b96a668] /opt/mqm/lib64/libmqmcs_r.so(xcsFFSTFn+0x1f4c)[0x7f1b5b96d39c] /opt/mqm/lib64/libmqmcs_r.so(xehExceptionHandler+0xe09)[0x7f1b5b 960de9] /lib64/libpthread.so.0(+0xf970)[0x7f1b5b08b970] /lib64/libc.so.6(+0x15cff6)[0x7f1b5ac02ff6] /opt/mqm/lib64/libmqmcs_r.so(xcsMemcpyFn+0x144)[0x7f1b5ba5f154] /opt/mqm/lib64/libmqml_r.so(kqiWaitForMessage+0x153e)[0x7f1b5c55 cc8e] /opt/mqm/lib64/libmqml_r.so(kpiMQGET+0x3df)[0x7f1b5c55f54f] /opt/mqm/lib64/libmqml_r.so(zsqMQGET+0x3db)[0x7f1b5c75912b] /opt/mqm/lib64/libmqml_r.so(zlsMQGET+0x363)[0x7f1b5c6f94f3] /opt/mqm/lib64/libmqml_r.so(zlsProcessMQIRequest+0x376)[0x7f1b5c 6fc126] /opt/mqm/lib64/libmqml_r.so(zlsProcessMessage+0x1de)[0x7f1b5c6f3 8fe] /opt/mqm/lib64/libmqml_r.so(zlsMainThread+0x1156)[0x7f1b5c6f4ad6 ] /opt/mqm/lib64/libmqmcs_r.so(+0x18d2d6)[0x7f1b5b9d72d6] /lib64/libpthread.so.0(+0x7e91)[0x7f1b5b083e91] /lib64/libc.so.6(clone+0x6d)[0x7f1b5abaa41d] MQM Function Stack zlsMainThread zlsProcessMessage zlsProcessMQIRequest zlsMQGET zsqMQGET kpiMQGET kqiWaitForMessage xcsMemcpy xcsFFST
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users who put messages outside of syncpoint may be affected by this issue. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When putting messages outside of syncpoint, MQ will attempt to pass messages directly to a waiting MQGET without first putting a message to the queue. A pool of buffers is used for this task which should be initialised before each use. One of the values associated with these buffers was not initialised between use and this led to a segmentation violation.
Problem conclusion
The code was modified so that memory was correctly initialised. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.1 CD 9.1.5 v9.1 LTS 9.1.0.4 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
IT29838
Reported component name
IBM MQ APPL M20
Reported component ID
5725S1400
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-07-25
Closed date
2019-10-25
Last modified date
2019-10-25
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
IBM MQ APPL M20
Fixed component ID
5725S1400
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
25 October 2019