APAR status
Closed as program error.
Error description
When an application uses a TOPIC with COMMINFO(xxx) MCAST(ENABLED) and client tracing is enabled then the application throws an FDC with a footprint similar to the following: | LVLS 						:- 7.5.0.6 									 						| | Product Long Name 	:- WebSphere MQ for Linux (x86-64 platform) 						| | Vendor 					:- IBM 													 ;				| | Installation Path 			:- /opt/mqm75 													 ;	| | Installation Name 		:- Installation4 (4) 			 											| | Probe Id 					:- XC130003 													 ;		| | Application Name 		:- MQM 													 ;			| | Component 				:- xehExceptionHandler 											| | SCCS Info 					:- /build/slot1/p750_P/src/lib/cs/unix/amqxerrx.c, 				| | Line Number 				:- 1433 													 ;			| | Build Date 					:- Feb 26 2016 					 									| | Build Level 				:- p750-006-160226 												| | Build Type 					:- IKAP - (Production) 												| | Program Name 			:- amqspubc 													 ;	| | Arguments 				:- 													 ;					| | Addressing mode 		:- 64-bit 													 ;			| | LANG 						:- en_US.UTF-8 													 ;	| | Process 					:- 7680 													 ;			| | Process(Thread) 			:- 7687 	 													 ;		| | Thread 						:- 3 													 ;				| | ThreadingModel 			:- PosixThreads 													 ;	| | UserApp 					:- TRUE 													 ;			| | Last HQC 					:- 0.0.0-0 													 ;			| | Last HSHMEMB 			:- 0.0.0-0 													 ;			| | Major Errorcode 			:- STOP 			 													 ;| | Minor Errorcode 			:- OK 													 ;				| | Probe Type 				:- HALT6109 													 ;	| | Probe Severity 				:- 1 													 ;				| | Probe Description 		:- AMQ6109: An internal WebSphere MQ error has occurred. 	| | FDCSequenceNumber 	:- 0 													 ;				| | Arith1 						:- 11 (0xb) 													 ;		| | Comment1 				:- SIGSEGV: address not mapped((nil)) 							| | 													 ;												|&# 09; +--------------------------------------------------------------- ----------------------------+ O/S Call Stack for current thread /opt/mqm75/lib64/libmqe_r.so(+0x2408de)[0x7fce9db008de] /opt/mqm75/lib64/libmqe_r.so(+0x25950d)[0x7fce9db1950d] /opt/mqm75/lib64/libmqe_r.so(+0x25818e)[0x7fce9db1818e] /opt/mqm75/lib64/libmqe_r.so(+0x25b920)[0x7fce9db1b920] /opt/mqm75/lib64/libmqe_r.so(+0x255b9e)[0x7fce9db15b9e] /lib64/libpthread.so.0[0x351c00f7e0] /opt/mqm75/lib64/libmqe_r.so(+0x2ebe9a)[0x7fce9dbabe9a] /opt/mqm75/lib64/libmqe_r.so(+0x56404e)[0x7fce9de2404e] /opt/mqm75/lib64/libmqe_r.so(+0x59e199)[0x7fce9de5e199] /opt/mqm75/lib64/libmqe_r.so(+0x5d66e4)[0x7fce9de966e4] /opt/mqm75/lib64/libmqe_r.so(+0x5d77ae)[0x7fce9de977ae] /opt/mqm75/lib64/libmqe_r.so(+0x2a8343)[0x7fce9db68343] /lib64/libpthread.so.0[0x351c007aa1] /lib64/libc.so.6(clone+0x6d)[0x351b8e893d] MQM Function Stack Rmm.send_stream_packets Rmm.send_single_packet Rmm.rmmSendPacket xcsFFST MQM Trace History { xcsRequestThreadMutexSem } xcsRequestThreadMutexSem rc=OK { xcsRequestThreadMutexSem } xcsRequestThreadMutexSem rc=OK { xcsReleaseThreadMutexSem } xcsReleaseThreadMutexSem rc=OK { xcsReleaseThreadMutexSem } xcsReleaseThreadMutexSem rc=OK { xihCSThreadClear -{ xcsEmptyCBM -} xcsEmptyCBM rc=OK } xihCSThreadClear rc=OK { xppInitialiseDestructorRegistrations } xppInitialiseDestructorRegistrations rc=OK { xcsInitialize -{ xihCSThreadClear --{ xcsEmptyCBM --} xcsEmptyCBM rc=OK -} xihCSThreadClear rc=OK -{ xcsRequestThreadMutexSem -} xcsRequestThreadMutexSem rc=OK -{ xcsRequestThreadMutexSem -} xcsRequestThreadMutexSem rc=OK -{ xcsReleaseThreadMutexSem -} xcsReleaseThreadMutexSem rc=OK -{ xcsGetEnvironmentString -} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND -{ xcsReleaseThreadMutexSem -} xcsReleaseThreadMutexSem rc=OK } xcsInitialize rc=OK { Rmm.send_stream_packets -{ Rmm.send_single_packet --{ Rmm.rmmSendPacket ---{ Rmm.sendmsg ---} Rmm.sendmsg rc=Unknown(4D) ---{ xcsFFST
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of MQ V7.5 or 8 with TOPICS that specify the MCAST(ENABLED) property. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: A programming error meant that it was possible for the MQ tracing routines to attempt to access a null pointer under the circumstances described above, resulting in a SIGSEGV signal being sent to MQ by the operating system.
Problem conclusion
The WebSphere MQ tracing routines have been corrected to avoid the SIGSEGV. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.5 7.5.0.7 v8.0 8.0.0.2 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
IT14460
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7241
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-24
Closed date
2016-04-21
Last modified date
2016-04-21
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
WMQ BASE MULTIP
Fixed component ID
5724H7241
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023