Fixes are available
APAR status
Closed as program error.
Error description
When the maxMsgSize on the get method call is equal to the size of the message on the queue, a MQRC_TRUNCATED_MSG_FAILED (rc=2080) error is seen when receiving the message. Instead the message should have been successfully received. The MQGET fails even though the trace shows that the maxMsgLength on the get was set to a value equal to the size of the message. The Java trace shows: 19:18:11.105 11 ----} JmqiEnvironment.conditionalCopyMQMD(MQMD,MQMD)() rc=0 19:18:11.105 11 readI32(): 2080 19:18:11.105 11 ?0x70467046? getReasonCode(boolean): 2080 19:18:11.105 11 readI32(): 2080 19:18:11.105 11 ?0x70467046? getReasonCode(boolean): 2080 19:18:11.105 11 readI32(): 25600
Local fix
As a workaround set the max message length on the get() method to a value higher than the length of the message being received. The get method to use is: MQQueue.get(MQMessage message,MQGetMessageOptions getMessageOptions,int maxMsgSize)
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ classes for Java V7 who get messages whilst specifying a maximum message size. Platforms affected: All Distributed (iSeries, all Unix and Windows) +Java **************************************************************** PROBLEM SUMMARY: When an attempt was made to receive a message whose size was equal to the maxMsgSize specified on the following method call: MQDestination_Object.get(MQMessage message, MQGetMessageOptions getMessageOptions, int maxMsgSize) a MQRC_TRUNCATED_MSG_FAILED was returned. This was because the WebSphere MQ Java implementation treated the maxMsgSize to be inadequate when it was equal to the size of the message being received.
Problem conclusion
The WebSphere MQ Java implementation has been modified to ensure that the MQRC_TRUNCATED_MSG_FAILED is not returned when the size of the message is equal to the maxMsgSize specified on the get method call. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.4 -------- -------------------- Windows U200323 AIX U835793 HP-UX (PA-RISC) U836458 HP-UX (Itanium) U836463 Solaris (SPARC) U836459 Solaris (x86-64) U836465 iSeries tbc_p700_0_1_4 Linux (x86) U836460 Linux (x86-64) U836464 Linux (zSeries) U836461 Linux (Power) U836462 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
IC69949
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
2010-07-15
Closed date
2010-07-27
Last modified date
2010-07-27
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