IBM Support

PI79863: DIFFERENT PREFIXES ARE USED FOR THE SAME NAMESPACE URL

Fixes are available

8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Different prefixes are used for the same namespace URL.  For
    example, in the following SOAP message:
    
    <soapenv:Fault>
      <faultcode>soapenv:Server</faultcode>
      <faultstring>DWLResponseException</faultstring>
        <detail>
          <port:processingFault
    xmlns:port="http://www.ibm.com/mdm/port">
          <axis2ns10:ResponseControl
    xmlns:axis2ns10="http://www.ibm.com/mdm/schema">
          </axis2ns10:ResponseControl>
          <axis2ns11:RequestType
    xmlns:axis2ns11="http://www.ibm.com/mdm/schema">
          </axis2ns11:RequestType>
          <axis2ns12:TxResult
    xmlns:axis2ns12="http://www.ibm.com/mdm/schema">
          </axis2ns12:TxResult>
        </port:processingFault>
      </detail>
    </soapenv:Fault>
    
    Different prefixes like <axis2nsXX> are used for the same
    namespace URL.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Different prefixes are used for the     *
    *                      same namespace URL.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Different prefixes are used for the same namespace URL.  For
    example, in the following SOAP message:
    <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>DWLResponseException</faultstring>
    <detail>
    <port:processingFault
    xmlns:port="http://www.ibm.com/mdm/port">
    <axis2ns10:ResponseControl
    xmlns:axis2ns10="http://www.ibm.com/mdm/schema">
    </axis2ns10:ResponseControl>
    <axis2ns11:RequestType
    xmlns:axis2ns11="http://www.ibm.com/mdm/schema">
    </axis2ns11:RequestType>
    <axis2ns12:TxResult
    xmlns:axis2ns12="http://www.ibm.com/mdm/schema">
    </axis2ns12:TxResult>
    </port:processingFault>
    </detail>
    </soapenv:Fault>
    Different prefixes like <axis2nsXX> are used for the same
    namespace URL.  This could cause OutOfMemory error.
    

Problem conclusion

  • Web services code has been updated to use the same prefix for
    the same namespace URL.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.14, 8.5.5.12 and 9.0.0.5.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI79863

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-12

  • Closed date

    2017-06-26

  • Last modified date

    2017-06-26

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022