APAR status
Closed as program error.
Error description
When a message arrives at the In terminal of an AggregateReply node, it is examined to see if it is an expected reply message. If Unknown Message Timeout property of the AggregateReply node is set then, a message that cannot be recognized immediately as a valid reply is held persistently in the integration node for the number of seconds that you specified as the Unknown Message Timeout property. If the unknown timeout interval expires, and the message is recognized, it is processed and If it is not recognized, the message is propagated to the Unknown terminal. But the AggregateReply node currently does not wait till the configured Unknown Message Timeout value to process the unrecognized messages and it can even cause the unrecognized messages to get discarded. For example, if Unknown Message Timeout property is set as '60' then it may wait only for 6 seconds to process the unrecognized message.
Local fix
Specify the Unknown Message Timeout property value as tenths of a second ie for using 6 second as the Unknown Message Timeout, set '60' as the Unknown Message Timeout property value in the AggregateReply node.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise V11.0 and V12.0 using the AggregateReply node. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When a message arrives at the 'In' terminal of an AggregateReply node, it is examined to see if it is an expected reply message. If Unknown Message Timeout property of the AggregateReply node is set then, a message that cannot be recognized immediately as a valid reply is held persistently in the integration node for the number of seconds specified as the Unknown Message Timeout property. If the unknown timeout interval expires, and the message is recognized, it is processed and If it is not recognized, the message is propagated to the Unknown terminal. But the AggregateReply node currently does not wait till the configured Unknown Message Timeout value to process the unrecognized messages and it can even cause the unrecognized messages to get discarded. For example, if Unknown Message Timeout property is set as '60' then it may wait only for 6 seconds to process the unrecognized message.
Problem conclusion
The product now correctly handles Unknown aggregate reply messages. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.0.0.20 v12.0 12.0.8.0 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
IT42402
Reported component name
APP CONNECT ENT
Reported component ID
5724J0550
Reported release
B00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-11-07
Closed date
2023-01-24
Last modified date
2023-01-24
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
APP CONNECT ENT
Fixed component ID
5724J0550
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 January 2023