IC66927: ADD DEBUG STATEMENTS TO MQ AND JMS BINDINGS TO ENABLE RESPONSE TIME TRACING

APAR status

• Closed as program error.

Error description

• Customers may require to measure the back-end response time of
  and application that is invoked through MQ/JMS Import Binding.
  This APAR will enable this lightweight tracing on the Import
  binding.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
  *                 or WebSphere Process Server v6.1.2 who       *
  *                 wish to trace response times with MQ and     *
  *                 JMS Bindings.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Customers may wish to trace response    *
  *                      times of backend services when using    *
  *                      MQ or JMS Bindings.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With this APAR, users are able to obtain trace showing
  request and response times with MQ or JMS Bindings.  Users
  need to enable to following trace strings:
  
  For MQ:
  
  SCA.MQ=fine
  
  For JMS:
  
  SCA.JMS=fine
  
  Once applied users will see trace with the following output
  for example:
  
  [08/03/10 16:45:42:906 GMT] 00000040 MQ            1
  com.ibm.ws.sca.internal.mq.handler.MQImportHandler  Start
  BindingMQ (IMPORT REQUEST)
  [08/03/10 16:45:43:156 GMT] 00000040 MQ            1
  com.ibm.ws.sca.internal.mq.MQMethodBindingImpl  End BindingMQ
  (IMPORT REQUEST Assoc(MessageID
  ID:414d5120514d2020202020202020202048c6944b20002502)
  Assoc(CorrelationID null))
  [08/03/10 16:45:43:343 GMT] 000000d2 MQ            1
  com.ibm.wsspi.sca.mq.inbound.MQInboundImpl  Start BindingMQ
  (EXPORT REQUEST Assoc(MessageID
  ID:414d5120514d2020202020202020202048c6944b20002502)
  Assoc(CorrelationID null))
  [08/03/10 16:45:43:406 GMT] 000000d2 MQ            1
  com.ibm.ws.sca.internal.mq.MQResponseSender  Start BindingMQ
  (EXPORT RESPONSE)
  [08/03/10 16:45:43:546 GMT] 000000d2 MQ            1
  com.ibm.ws.sca.internal.mq.MQResponseSender  End BindingMQ
  (EXPORT RESPONSE Assoc(MessageID
  ID:414d5120514d2020202020202020202048c6944b20002602)
  Assoc(CorrelationID
  ID:414d5120514d2020202020202020202048c6944b20002502))
  [08/03/10 16:45:43:562 GMT] 000000d2 MQ            1
  com.ibm.wsspi.sca.mq.inbound.MQInboundImpl  End BindingMQ
  (EXPORT REQUEST)
  [08/03/10 16:45:43:578 GMT] 000000d2 MQ            1
  com.ibm.wsspi.sca.mq.inbound.MQResponseListenerImpl  Start
  BindingMQ (IMPORT RESPONSE Assoc(MessageID
  ID:414d5120514d2020202020202020202048c6944b20002602)
  Assoc(CorrelationID
  ID:414d5120514d2020202020202020202048c6944b20002502))
  [08/03/10 16:45:49:578 GMT] 000000d2 MQ            1
  com.ibm.wsspi.sca.mq.inbound.MQResponseListenerImpl  End
  BindingMQ (IMPORT RESPONSE)
  

Problem conclusion

• The code was modified to add trace statements to the
  MQ/JMS import and export that log the message id and
  correlation id that can be used to correlate requests and
  responses.
  
  There are no known side effects associated with this fix.
  There is no known alternative workaround should you encounter
  this problem.
  
  This code fix was targeted to be included in the following fix
  packs:
  
       6.1.2.4 Fix Pack 2 (v6.1.2.4)
  

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

  WEB ESB FOR WIN

• Fixed component ID

  5724I8200

Applicable component levels

• R100 PSN

     UP

• R200 PSN

     UP

• R300 PSN

     UP

• R612 PSY

     UP

• R620 PSN

     UP

• R700 PSN

     UP