IBM Support

IT47852: FOLLOWING APAR IT47319 THERE ARE STILL SOME SCENARIOS WHERE SCHEMAS CLASH

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Where an application includes multiple libraries which in turn
    contain schemas which have the same unqualified filename, but
    these schemas do not contain global elements with the same
    identifier then it is possible to erroneously receive the
    following error message:
    BIP4395E: Java exception: 'org.apache.xerces.xni.XNIException';
    thrown from class name:
    'com.ibm.broker.schemamgr.MbSchemaCompilerCL', method name:
    'error', file: 'MbSchemaCompilerCL.java', line: '587'
    This problem is similar to that reported in IT47319, however the
    fix for that APAR did not catch all possible occurences.
    

Local fix

  • Rename the xsd in one of the libraries.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise version 12 or higher
    using XML Schemas.
    
    
    Platforms affected:
    AIX, LinuxZ64, LinuxX64, LinuxPPCLE64
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Where an application includes multiple libraries which in turn
    contain schemas which have the same unqualified filename, but
    these schemas do not contain global elements with the same
    identifier then it is possible to erroneously receive the
    following error message:
    
    BIP4395E: Java exception:
    'org.apache.xerces.xni.XNIException'; thrown from class name:
    'com.ibm.broker.schemamgr.MbSchemaCompilerCL', method name:
    'error', file: 'MbSchemaCompilerCL.java', line: '587'
    
    This
    problem is similar to that reported in IT47319, however the fix
    for that APAR did not catch all possible occurences.
    

Problem conclusion

  • Schemas of this form no longer produce an error message as long
    as there are no global elements that have name clashes.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version   Maintenance Level
    v12.0      12.0.12.13
    v13.0      13.0.3.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT47852

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0560

  • Reported release

    C00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-03-17

  • Closed date

    2025-03-20

  • Last modified date

    2025-03-20

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0560

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C00","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
20 March 2025