IT18477: MQINPUT NODE THREAD CONTEXT NOT CORRECTLY INITIALIZED AFTER RE-DEPLOY

APAR status

• Closed as program error.

Error description

• After a re-deploy if a thread is re-used for a new instance of
  an MQInput node then a value to uniquely identify the MQ
  connection used by the input node is not set on the thread
  context. This means that if an MQOutput node is set to pass on
  the message context from the incoming message then it will not
  be able to find it and so creates a new default context.
  
  This could be visible to the user as the UserIdentifier found
  in the outgoing MQMD would be the userid of the integration
  server process rather than that present in the incoming message.
  
  
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus V10 using the MQOuput node in a
  pair with an MQInput node, and the passIdentity or passAll
  context settings.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  After a re-deploy if a thread is re-used for a new instance of
  an MQInput node then a value to uniquely identify the MQ
  connection used by the input node is not set on the thread
  context. This means that if an MQOutput node is set to pass on
  the message context from the incoming message then it will not
  be able to find it and so creates a new default context.
  
  This could be visible to the user as the UserIdentifier found
  in the outgoing MQMD would be the userid of the integration
  server process rather than that present in the incoming message.
  
  
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0.  For details
  visit
  http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
  tools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product now correctly initialises the MQInput node thread
  context after a re-deploy.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.9
  
  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