IT37248: UNKNOWN AGGREGATION REPLIES IN MESSAGE FLOW THAT ALSO USES CLIENT MQ CONNECTIONS

APAR status

• Closed as program error.

Error description

• When using the aggregation nodes with a local default IBM MQ
  queue manager in message flows that also use client MQ
  connections, it is possible that fan-in aggregation reply
  messages are received via the client MQ connections before the
  aggregation request has been committed to the local queue
  manager. If this occurs, replies are sent to the Unknown
  terminal of the AggregationReply node.
  
  The message flow does not distinguish between local and remote
  MQ connections when committing transactions, the order is the
  same as the order that the connections are used.
  

Local fix

• Increase the Unknown Message Timeout property value on the
  AggregationReply node.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise V11 and V12 using the
  Aggregation nodes.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using the aggregation nodes with a local default IBM MQ
  queue manager in message flows that also use client MQ
  connections, it is possible that fan-in aggregation reply
  messages are received via the client MQ connections before the
  aggregation request has been committed to the local queue
  manager. If this occurs, replies are sent to the Unknown
  terminal of the AggregationReply node.
  
  The message flow does not distinguish between local and remote
  MQ connections when committing transactions, the order is the
  same as the order that the connections are used.
  

Problem conclusion

• The product has been modified with an option to ensure that
  resources on the default queue manager are committed first.
  Either set and export the environment variable
  MQSI_COMMIT_DEFAULT_QUEUE_MANAGER_FIRST to any value, or update
  the server.conf.yaml file with the following under the
  MQConnectionManager section of ResourceManagers:
  
  ResourceManagers:
    MQConnectionManager:
      defaultQMCommitSequence: 59            # Determines the
  relative order of commit for default MQ links; set to 59 for
  commit before other queue managers, and 62 for after them.
  
  The resource managers used in a message flow are committed in
  priority order, with the standard MQ connection MQCMIT happening
  at priority 60, and committing individual QM connections in
  order of use. Setting defaultQMCommitSequence to 59 moves the
  MQCMIT call for the default queue manager to just before the
  rest of the queue managers. Setting defaultQMCommitSequence to
  62 would place it immediately after the rest of the queue
  managers.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.14
  v12.0      12.0.2.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 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