IBM Support

IT28789: ADAPTERCLASSLOADER NOT INITIALISED FOR IDOC GATEWAY PATTERN

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

  • It is possible to deploy flows which parse SAP Idocs using the
    DataObject parser in an Integration Server that does not contain
    any adapter components.
    In these circumstances the AdapterClassLoader is not correctly
    initialized and when processing a message the following error
    will occur:
    2019-03-28 13:44:46.897088Z: [Thread 180] (Msg 4/4) BIP4395E:
    Java exception:'java.lang.NoClassDefFoundError'; thrown from
    class name: 'com.ibm.j2ca.sap.records.SAPParseRecord', method
    method name: 'getNext',file: 'SAPParseRecord.java', line: '187'
    Examining service trace will show that the missing class is
    JCOException.
    
    The service trace will also show that the jarsURL is being set
    to a null value:
    
    MbAdapterDirector.loadAdapterExternalResourceFilesForSAP,
    'setting 'adapterExternalResourceJarsURLs' to ', ''
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of App Connect Enterprise v11 using the DataObject
    domain to parse IDocs.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">It is possible
    to deploy flows which parse SAP IDocs using the </span><span
    style="background-color:rgb(255, 255, 255)">DataObject parser in
    an Integration Server that does not contain </span><span
    style="background-color:rgb(255, 255, 255)">any Adapter
    components as long as the jarsURL and nativeLibs parameters are
    correctly completed in the SAPConnectorProvider stanza of the
    server.conf.yaml or node.conf.yaml file.
                                        </span>
    
    <span style="background-color:rgb(255, 255, 255)">In these
    circumstances the AdapterClassLoader is not correctly
    </span><span style="background-color:rgb(255, 255,
    255)">initialized and when processing a message the following
    error w</span><span style="background-color:rgb(255, 255,
    255)">ill occur:
                                                       </span>
    
    <span style="background-color:rgb(255, 255, 255)">2019-03-28
    13:44:46.897088Z: [Thread 180] (Msg 4/4) BIP4395E:  </span><span
    style="background-color:rgb(255, 255, 255)">Java
    exception:'java.lang.NoClassDefFoundError'; thrown from
    </span><span style="background-color:rgb(255, 255, 255)">class
    name: 'com.ibm.j2ca.sap.records.SAPParseRecord', method
    </span><span style="background-color:rgb(255, 255, 255)">method
    name: 'getNext',file: 'SAPParseRecord.java', line: '187'</span>
    
    <span style="background-color:rgb(255, 255, 255)">Examining
    service trace will show that the missing class is </span><span
    style="background-color:rgb(255, 255, 255)">JCOException.
                                                     </span>
    
    <span style="background-color:rgb(255, 255, 255)">The service
    trace will also show that the jarsURL is being set t</span><span
    style="background-color:rgb(255, 255, 255)">o a null value:
                                             </span>
    <span style="background-color:rgb(255, 255,
    255)">MbAdapterDirector.loadAdapterExternalResourceFilesForSAP,
    </span><span style="background-color:rgb(255, 255, 255)">
    </span><span style="background-color:rgb(255, 255,
    255)">'setting 'adapterExternalResourceJarsURLs' to ', ''
               </span>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT28789

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-12

  • Closed date

    2019-09-30

  • Last modified date

    2019-09-30

  • 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

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 September 2019