Fixes are available
APAR status
Closed as program error.
Error description
You have multiple queue managers on a server. Shortly after you startup one queue manager you get FDC files from another queue manager showing- . Probe Id :- XY324103 Application Name :- MQM Component :- xstGetSubpoolsLock Program Name :- amqrmppa Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Minor Errorcode :- OK Probe Type :- MSGAMQ6119 Probe Severity :- 2 Probe Description :- AMQ6119 An internal WebSphere MQ error has occurred ('43 - Identifier removed' from semop.) Arith1 :- 43 (0x2b) Comment1 :- '43 - Identifier removed' from semop. . SemID passed to semop 0x457ed40 00000000 . The FDCs are complaining about an IPC semaphore (the "subpools semaphore") with semid of 0 being unexpectedly missing. In almost all cases this is due to ipcrm being run, however it has been discovered that during start up there is a slight possibility MQ could mis-identify ownership of the subpools semaphore and remove another queue managers subpools semaphore. Additional FDC's may also include: Probe Id :- XY324102 Component :- xstGetSubpoolsLock Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred ('3021 - The value specified for the argument is not correc' from semop.) Arith1 :- 3021 0x'bcd' Arith2 :- 0 Comment1 :- '3021 - The value specified for the argument is not correc' from semop Probe Id :- XY324103 Component :- xstGetSubpoolsLock Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred ('3507 - Object too large.' from semop.) Arith1 :- 3507 0x'db3' Arith2 :- 0 Comment1 :- '3507 - Object too large.' from semop. . Additional keywords: AMQ6109 . Also see IT03168.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: You may be impacted by this problem if you reboot any time after a queue managers ended badly, that is without completion of endmqm. There would then be a small chance that you could get misidentification of a semaphore set when that queue started. Platforms affected: All Unix **************************************************************** PROBLEM SUMMARY: This issue was due to inadvertent omission of a check of the semaphore create time, for subpools semaphore sets. That omission can then lead to mis-identification of ownership of a semaphore set. That would only occur if a queue manager ended badly (that is, other than via endmqm), which would prevent the queue manager cleaning up its semaphore sets. In addition, the semaphore set would have to then get deleted, possibly by a reboot or manual use of ipcrm. Then, to encounter the problem another queue manager would have to, by chance, be given that same-numbered semaphore set. And finally, the original queue manager would then have to be restarted.
Problem conclusion
Ensured that a check for the semaphore set create time is made when identifying semaphore sets. Added additional diagnostics to assist if there are any other issues in this area. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.12 v7.1 7.1.0.5 v7.5 7.5.0.3 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
IV47710
Reported component name
WMQ LIN X86 V7
Reported component ID
5724H7224
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-29
Closed date
2013-09-16
Last modified date
2014-12-15
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 LIN X86 V7
Fixed component ID
5724H7224
Applicable component levels
R700 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0"}]
Document Information
Modified date:
01 October 2021