IT13795: DATAPOWER WEBSERVICE PROXY WITH MQ FSH REQUEST MATCHING LOGIC MIGHT STRUGGLE WITH AMBIGUOUS RESULTS ALSO VISIBLE IN LOGS

Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower B2B Appliance version 7.0
Fix packs for DataPower Integration Appliance version 7.0
Fix packs for DataPower Gateway version 7.1
Fix packs for DataPower Gateway version 7.2
Fix packs for DataPower Gateway version 7.5
Fix packs for DataPower Gateway version 7.5.1

APAR status

• Closed as program error.

Error description

• The user observed problems with DataPower WebService Proxy
  having MQ Front side Handler. In certain scenarios, the logs
  showed request matching attempts to an unrelated WSP MQ FSH in
  another application domain. In some situations, the match to
  the actual target WSP (or any other WSP) even failed, due to
  missed match criteria.
  

Local fix

Problem summary

• MQ Web Service Proxy requests result in a Port value of 0. If
  all other unique identifiers such as URL IP and Operation are
  the same the request may go to the first compiled WSDL.
  

Problem conclusion

• Fix is available in 7.0.0.13, 7.1.0.10, 7.2.0.6 and 7.5.0.2
  
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

Temporary fix

• Create another unique identifier if using MQ for a Front Side
  Handler on a Web Service Proxy
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• 0
  

Fix information

• Fixed component name

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels

• R720 PSY

     UP