PM74821: HANG ON CLIENT SIDE FOR WEBSERVICE USING AXIS2, MTOM AND WS-SECURITY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer is implementing Webservice with MTOM and WS-SECURITY
  and java/axis2. Testing with soapUI no answer received.
  
  Auxtrace show:
  PI 1700 PITC ENTRY FUNCTION(TRUST_CLIENT) WSSE_PROGRAM(DFHWSSE1)
                     MODE(PROVIDER) DIRECTION(BACKWARD)
  PI 1700 PITC ENTRY FUNCTION(TRUST_CLIENT)
                     CHANNEL_TOKEN(1C68F030) POOL_TOKEN(1C690030)
                     WSSE_PROGRAM(DFHWSSE1) WSSE_CONFIG(1C67D1E0
                    , 00000A11) MODE(PROVIDER) DIRECTION(BACKWARD)
  TR 0101 TRPT  *EXC* - OVERLENGTH-ENTRY : CALLING DOMAIN WAS PI :
                     PARAMETER LIST WAS FUNCTION(TRACE_PUT)
                     POINT_ID(170E) DATA1 (1C259CEC , 00000040)
                     DATA2(1C5143B8 , 0000424F) DATA3(1C2590D4
                     , 00000004)
  
  Trace entry PI 170E is Message parsing error.
  
  faultcode wsse:Inv@lidSecurity with faultstring There was an
  error processing the wsse:Security Header are send in response.
  

Local fix

• NO
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: SOAP Fault returned when a CICS         *
  *                      provider PIPELINE is configured         *
  *                      to use Axis2, MTOM and WS-Security.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CICS uses a provider pipeline with Axis2(MTOM) and WS-Security
  for the webservice. WS-Security processing is being called to
  process the response that has been created by Axis2. Parsing
  of the response fails because it is not pure XML data, it is
  an HTTP response containing MTOM message. The failure to parse
  the message causes DFHPITC to return an exception response back
  to the pipeline and that leads to the SOAP Fault being
  returned.
  Trace entry PI170E is then being issued without a limit on the
  length of data2. The data2 field contains the document being
  parsed, so for a long document this produces an overlength
  trace entry (TR0101).
  

Problem conclusion

• DFHPITC has been changed to return without doing anything if
  this is the provider or requester pipeline going backwards.
  Additionally, the size of the data2 field for trace entry TR170E
  is limited to 2KB.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  UK90783 PM80278

Modules/Macros

•    DFHPITC
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R700 PSY UK90783

     UP13/01/11 P F301

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.