IT17875: NAMING THE ENVIRONMENT TREE IN AN MQGET NODE OUTPUT DATA LOCATION CAN CAUSE THE INTEGRATION SERVER TO ABEND

APAR status

• Closed as program error.

Error description

• When using an MQGet node in a message flow it is possible to
  specify an Environment tree path as the output data location,
  where the message retrieved will be stored.
  
  A defect exists such that the underlying message data the
  Environment parsers are dependent on is deleted by the MQGet
  node when its evaluation is complete and the flow logic returns
  to the previous node that called the MQGet node. This can lead
  to descoped memory being accessed when the Environment tree is
  subsequently read and can result in the integration server
  abending.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10.0 setting the output data
  location of an MQGet node to the Environment tree.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using an MQGet node in a message flow it is possible to
  specify an Environment tree path as the output data location
  where the message retrieved will be stored. When the Environment
  tree is used as the output data location, the message tree can
  be in scope for a longer period than the MQGet node was
  evaluated for.
  
  For example, if the MQGet node is invoked like a function call
  using a MbRoute call from a Java Compute node, when the message
  flow returns to an earlier point in the processing the MQGet
  node's output will still be available in the Environment tree
  but the MQGet node is no longer on the call stack. A defect
  exists such that the underlying message data the Environment
  parsers are dependent on is deleted by the MQGet node when its
  evaluation is complete and the flow logic returns to the
  previous node that called the MQGet node. This can lead to
  descoped memory being accessed when the Environment tree is
  subsequently read and can result in the integration server
  abending.
  

Problem conclusion

• The product has been corrected so that the MQGet node no longer
  deletes the message data that the Environment tree parsers are
  dependent on. Therefore when the processing returns to a calling
  node in the message flow the MQGet result can still be accessed
  through the message tree.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.7
  v8.0       8.0.0.9
  v9.0       9.0.0.7
  
  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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP