Fixes are available
APAR status
Closed as program error.
Error description
This APAR is a cumulative fix for problems found in publish/subscribe, including prevention of memory leaks, performance improvements when wildcard subscriptions are used and fixes to coding errors. These problems are described separately below.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of publish/subscribe functionality Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: This addresses a number of individual problems found in publish/subscribe and are listed below. Note: This APAR is not available as an interim fix on any earlier fix pack, and is not suitable to be supplied as one.
Problem conclusion
IV12219.2 Abstract: MQOPEN OF TOPIC SLOW. LARGE NUMBER OF TOPICS. UNUSED TOPICS NOT REMOVED. INCREASING SHARED MEMORY USAGE. Users Affected: Users of publish/subscribe, publishing unique data in topic strings, with wildcard subscriptions matching those topic strings. Platforms affected: All Distributed (iSeries, all Unix and Windows) Error Description: If messages are published to unique topic strings and a wildcard subscription matches each topic string then the topic tree will continue to grow. Each topic will be considered in use because it has an active subscriber and so will never be removed. This can eventually have an adverse effect on the performance of publish/subscribe, including the MQOPEN of a topic string. It will also lead to a continual increase in shared memory usage. The following runmqsc command will return a large number of topics: DISPLAY TPSTATUS('#') TYPE(TOPIC) Problem Summary: Topics were not considered to be unused if had wildcard subscriptions even if the topic string had not been published to in 30 minutes (or the current setting of the TREELIFE queue manager attribute). Problem Conclusion: If a topic is considered unused except for one or more wildcard subscriptions it will be removed. ---------------------------------------------------------------- IV12219.4 Abstract: FDC GENERATED BY AMQFCXBA PROCESS XC130031 ACCESS VIOLATION IN KQITOPICREGISTERSUBSCRIBER USING SUB NAMES Users Affected: Customers using the queued pub/sub interface Platforms affected: All Distributed (iSeries, all Unix and Windows) Error Description: When using subscription names with the queued pub/sub interface an Access Violation is encountered in the amqfcxba process. An FDC is generated, with a function stack similar to the following: MQM Function Stack fpiTaskReply faxRunStream faiControlThread faiProcessCommandMsg faiRegisterSubscriber lpiSPISubscribe zstMQSUB zifMQSUB zsqMQSUB kpiMQSUB kqiSubscribeTopic kqiAlterSubscription kqiRegisterSubscriber kqiTopicRegisterSubscriber xcsFFST Problem Summary: An incorrect calculation led to too much data being copied, causing an array bounds exception. Problem Conclusion: The calculation was corrected so that the correct amount of data is copied. ---------------------------------------------------------------- IV12219.9 Abstract: QUEUED PUB/SUB INTERFACE INCORRECTLY ADDS QMGRNAME AND QNAME MQRFH1 MQRFH2 Users Affected: Users of the queued pub/sub interface. Platforms affected: All Distributed (iSeries, all Unix and Windows) Error Description: The queued pub/sub interface omitted the MQPSQMgrName and MQPSQName tags from messages delivered to MQRFH1 subscribers when they were supplied in the publication message. The queue pub/sub interface also caused the QMgrName and QName tags to be empty or be duplicated for messages delivered to MQRFH2 subscribers when they were supplied in the publication message. Problem Summary: The queued pub/sub interface was incorrectly processing the publication. Problem Conclusion: The queued pub/sub interface now correctly generates the message for MQRFH1 and MQRFH2 subscribers. ---------------------------------------------------------------- --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.8 -------- -------------------- Windows U200335 AIX U845856 HP-UX (PA-RISC) U847965 HP-UX (Itanium) U847970 Solaris (SPARC) U847966 Solaris (x86-64) U847972 iSeries 7.0.1.8 Linux (x86) U847967 Linux (x86-64) U847971 Linux (zSeries) U847968 Linux (Power) U847969 v7.1 Platform Fix Pack 7.1.0.1 -------- -------------------- Windows 7.1.0.1 AIX 7.1.0.1 HP-UX (PA-RISC) 7.1.0.1 HP-UX (Itanium) 7.1.0.1 Solaris (SPARC) 7.1.0.1 Solaris (x86-64) 7.1.0.1 iSeries 7.1.0.1 Linux (x86) 7.1.0.1 Linux (x86-64) 7.1.0.1 Linux (zSeries) 7.1.0.1 Linux (Power) 7.1.0.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
IV12219
Reported component name
WMQ AIX V7
Reported component ID
5724H7221
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-14
Closed date
2012-01-24
Last modified date
2012-01-24
APAR is sysrouted FROM one or more of the following:
PM47710
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ AIX V7
Fixed component ID
5724H7221
Applicable component levels
R701 PSY
UP
[{"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.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023