APAR status
Closed as program error.
Error description
The following series of events will lead to out of order message processing when the gateway is configured with in-order processing mode. The latter mode specifies that all messages should be output in exactly the same order as they have been received from input queue. 1. Message #1 is received and being processed. 2. Message #2 is received and being processed. 3. Message #2 reaches back side first, acquires an instance of MQQM object to allocate back side connection and then goes dormant waiting for Message #1 to be processed. 4. MQQM is disabled. 5. Message #1 reaches back side, unable to allocate MQQM object (it is already disabled) and fails. 6. At this point processing of Message #1 considered to be finished and Message #2 proceeds without checking that Message #1 has failed.
Local fix
Problem summary
Handle all connection state changes.
Problem conclusion
The fix will be in 3.7.3.16, 3.8.0.10, 3.8.1.9, 3.8.2.1
Temporary fix
Comments
APAR Information
APAR number
IC72872
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
380
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-30
Closed date
2011-01-20
Last modified date
2011-01-21
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
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
R373 PSY
UP
R380 PSY
UP
R381 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.8","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022