Fixes are available
APAR status
Closed as program error.
Error description
A WMQ V7 base java application issues the API call MQQueue.close() with the MQCO_DELETE option. This results in RC=2055 (MQRC_Q_NOT_EMPTY). This behavior is expected since the permanent dynamic queue is not empty. Next, the MQQueue.close() call is issued with the option MQCO_DELETE_PURGE. This fails with the reason code 2019 - MQRC_HOBJ_ERROR. The following exception is thrown: Caused by: com.ibm.mq.MQException: MQJE001: Exit code '2', Cause '2019'. . Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2019
Local fix
Only call MQQueue.close() with the MQCO_DELETE_PURGE option, as opposed to calling MQQueue.close() with MQCO_DELETE, receiving the 2055 error and then re-issuing it with the MQCO_DELETE_PURGE option.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ v7 classes for Java, who attempt to delete a permanent dynamic queue using the MQQueue.close() call with the MQCO_DELETE_PURGE option, when the attempt to delete the same permanent dynamic queue using the MQQueue.close() call with MQCO_DELETE has previously failed with RC=2055 (MQRC_Q_NOT_EMPTY). Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: The application issues an MQQueue.close() call with MQCO_DELETE, which fails with the reason MQRC_Q_NOT_EMPTY (2055) as the permanent dynamic queue being deleted is not empty due to the committed message on this queue. During this close call, the WebSphere MQ Classes for Java reset the internal MQ queue reference (the "hobj"). This was incorrect,as the returned error is indicated that the queue had not been closed, and that the application may wish to re-issue the close call with the purge option. When the application issues the MQQueue.close() call with the MQCO_DELETE_PURGE option, this fails with reason MQRC_HOBJ_ERROR (2019), as the internal reference to the queue has been reset.
Problem conclusion
The WMQ V7 Java client code has been changed to ensure that when MQQueue.close() is invoked with the MQCO_DELETE option, it does not reset the Object(Queue) reference. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.6 -------- -------------------- Windows U200328 AIX U840698 HP-UX (PA-RISC) U841555 HP-UX (Itanium) U841560 Solaris (SPARC) U841556 Solaris (x86-64) U841562 iSeries tbc_p700_0_1_6 Linux (x86) U841557 Linux (x86-64) U841561 Linux (zSeries) U841558 Linux (Power) U841559 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
IC76104
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-02
Closed date
2011-06-06
Last modified date
2011-06-09
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 WINDOWS V7
Fixed component ID
5724H7220
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