IC68896: JXPATH EXCEPTION ON ESB MESSAGE ELEMENT SETTER

WebSphere Enterprise Service Bus V7.0.0 Fix Pack 3 (7.0.0.3)
WebSphere Enterprise Service Bus V7.0.0 Fix Pack 4 (7.0.0.4)

APAR status

• Closed as program error.

Error description

• WESB cannot retrieve xpath information from SOAPHeader for
  userInfo, since it becomes null.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Websphere Enterprise Service Bus    *
  *                 or WebSphere Process Server v6 or v7 who     *
  *                 attempt to access data from the SOAPHeader   *
  *                 with the Message Element Setter primitive    *
  *                 in a multi-threaded environment.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: WESB cannot retrieve xpath              *
  *                      information from SOAPHeader for         *
  *                      userInfo, since it seems to become      *
  *                      null in a multi-threaded environment.   *
  ****************************************************************
  * RECOMMENDATION: If you encounter this problem then you are   *
  *                 advised to install the code fix associated   *
  *                 with this APAR.                              *
  ****************************************************************
  The issue is in the initialisation of jxpath compiled
  expressions when multiple threads are used:
  Stack Dump = org.apache.commons.jxpath.JXPathException:
  No value for
  xpath: /headers/SOAPHeader[name='number']/value
  at
  org.apache.commons.jxpath.ri.JXPathContextReferenceImpl.getValue
  
  (JXPathContextReferenceImpl.java:344)
  at
  org.apache.commons.jxpath.ri.JXPathCompiledExpression.getValue
  (JXPathCompiledExpression.java:57)
  
  The exception is thrown even though the value at the specified
  xpath does exist and is a known problem in jxpath version 1.2.
  
  We have worked around the problem by synchronizing the initial
  WESB method that calls the jxpath method.
  

Problem conclusion

• The code was modified to synchronise the initial WESB Method
  that calls the JXPath method.
  
  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.0 Fix Pack 5 (v6.1.0.5)
  6.1.2 Fix Pack 4 (v6.1.2.4)
  6.2.0 Fix Pack 4 (v6.2.0.4)
  7.0.0 Fix Pack 3 (v7.0.0.3)
  

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 PSY

     UP

• R612 PSY

     UP

• R620 PSY

     UP

• R700 PSY

     UP