Fixes are available
APAR status
Closed as program error.
Error description
If a WebSphere MQ Java application uses a security exit which returns an empty array (byte [0]) after previously returning a non-empty array, the data transmitted to the queue manager may indicate data is to follow, whereas no data does. If a queue manager security exit requests a channel to be closed, the WebSphere MQ Java client application returns an incorrect error (MQRC_CONNECTION_BROKEN) to the application. Also, when using security exits with the WebSphere MQ Version 7 Explorer, an error may be returned when attempting to connect to a queue manager.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ Java or Java Message Service (JMS) client, and/or the WebSphere MQ Explorer who use security exits. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: There are a number of issues here: - WebSphere MQ Java and JMS clients do not always set the data length size when sending data to the queue manager. - The case where the queue manager security exit closes the channel was not handled by WebSphere MQ Java or JMS clients. - The WebSphere MQ Explorer passed a null value to the Java or JMS client, which resulted in a NullPointerException being thrown when attempting to connect to a queue manager.
Problem conclusion
The WebSphere MQ Java and JMS clients have been updated to always set the data length. The case where the queue manager security exit closes the channel is now correctly reported as a MQRC_CHANNEL_NOT_AVAILABLE (2537) error. A check was introduced to prevent NullPointerExceptions occurring when using the WebSphere MQ Explorer with security exits. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.0.2 -------- -------------------- Windows U200302 AIX U822354 HP-UX (PA-RISC) U822349 HP-UX (Itanium) U822351 Solaris (SPARC) U822353 Solaris (x86-64) U822394 iSeries tbc_p700_0_0_2 Linux (x86) U822348 Linux (x86-64) U822393 Linux (zSeries) U822352 Linux (Power) U822350 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
IC58936
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-14
Closed date
2009-01-28
Last modified date
2009-01-28
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
R700 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","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023