APAR status
Closed as program error.
Error description
The rollback of a large segmented MQ message can result in an MQRC of MQRC_MSG_TOO_BIG_FOR_Q (2030) or MQRC_MSG_TOO_BIG_FOR_Q_MGR (2031) errors. This will cause the segmented messages to remain on the input queue and as such the message flow cannot process any further messages.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10.0 using MQ input nodes sending segmented MQ messages where the total cumulative size of the message segments sent exceed the MQ queue or queue manager maximum size setting. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When an MQInput node retrieves messages from its input queue it specifies the MQGMO_COMPLETE_MSG option. This means that if the input queue has segmented messages on it then the queue manager will return a single MQ message containing all of the segments. When a message flow detects that the input message has exceeded its backout count then it will attempt to put the message to the input queues Backout queue (if one is defined) or to the DLQ (if the queue manager has one). With all of the message segments now in one message buffer, the resultant message can be too large for the queue and/or the queue manager. This can result in an MQRC of MQRC_MSG_TOO_BIG_FOR_Q (2030) or MQRC_MSG_TOO_BIG_FOR_Q_MGR (2031). This will cause the segmented messages to remain on the input queue and as such the message flow cannot process any further messages.
Problem conclusion
The product has been corrected so that the resultant large message is put to the Backout queue or DLQ with MQMF_SEGMENTATION_ALLOWED. This means the queue manager will split the large message up if it needs to. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.10 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT20272
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-27
Closed date
2017-08-31
Last modified date
2017-08-31
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
RA00 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020