IBM Support

IT34080: EXCESSIVE ERROR LOGGING TO STDOUT WHEN DELIMITER FOR SAP ALE PASSTHROUGH IS INVALID

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

  • When creating an outbound adapter for SAP Ale Idoc Passthrough
    scenarios it is possible to specify a custom delimiter. If this
    delimiter is invalid, particularly if it starts with "\\" but
    is not either "\\n" or "\\r\\n" then the following stack trace
    is logged for every message processed by the adapter:
    
    com.ibm.j
    2ca.sap.exception.SapAleOutboundException
    E
    2020-07-27T17:24:24.
    203145623Z 2020-07-27 13:24:24.202 44 at com.ibm.j2ca.sap.ale.id
    oc.PassThroughIDoc.setDelimiter(PassThroughIDoc.java:288)
    E
    2020
    -07-27T17:24:24.203157980Z 2020-07-27 13:24:24.202 44 at com.ibm
    .j2ca.sap.ale.outbound.PassThroughAleInvoker.buildIdoc(PassThrou
    ghAleInvoker.java:153)
    E
    2020-07-27T17:24:24.203164210Z
    2020-07-27 13:24:24.202 44 at com.ibm.j2ca.sap.ale.outbound.Pass
    ThroughAleInvoker.postIdoc(PassThroughAleInvoker.java:89)
    E
    2020
    -07-27T17:24:24.203170137Z 2020-07-27 13:24:24.202 44 at com.ibm
    .j2ca.sap.ale.outbound.AleInvoker.execute(AleInvoker.java:123)
    E
    
    2020-07-27T17:24:24.203175820Z 2020-07-27 13:24:24.202 44 at co
    m.ibm.j2ca.sap.SAPInteraction.getOutputRecord(SAPInteraction.jav
    a:284)
    E
    2020-07-27T17:24:24.203181884Z 2020-07-27 13:24:24.203
    44 at com.ibm.j2ca.sap.SAPInteraction.doExecute(SAPInteraction.j
    ava:118)
    E
    2020-07-27T17:24:24.203270678Z 2020-07-27
    13:24:24.203 44 at com.ibm.j2ca.base.WBIInteraction.execute(WBII
    nteraction.java:522)
    E
    2020-07-27T17:24:24.203298024Z
    2020-07-27 13:24:24.203 44 at com.ibm.broker.adapter.deploy.MbAd
    apterAccess.execute(MbAdapterAccess.java:188)
    E
    2020-07-27T17:24
    :24.203303904Z 2020-07-27 13:24:24.203 44 at com.ibm.broker.adap
    ter.nodes.MbAdapterRequestNode.requestData(MbAdapterRequestNode.
    java:589)
    E
    2020-07-27T17:24:24.203309634Z 2020-07-27
    13:24:24.203 44 at com.ibm.broker.plugin.MbRequestTemplateNode.r
    equestData(MbRequestTemplateNode.java:60)
    E
    2020-07-27T17:24:24.
    800862119Z 2020-07-27 13:24:24.799 44
    com.ibm.j2ca.sap.exception.SapAleOutboundException
    E
    
    This can
    flood the logs, especially on container based systems where the
    stdout/stderr streams are forwarded to a log consumer.
    

Local fix

  • Correct the Adapter to use a valid delimiter.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11 using the SAP Request Node in Ale IDoc
    Passthrough mode.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When creating
    an outbound adapter for SAP Ale IDoc Passthrough </span><span
    style="background-color:rgb(255, 255, 255)">scenarios it is
    possible to specify a custom delimiter. If this </span><span
    style="background-color:rgb(255, 255, 255)">delimiter is
    invalid, particularly if it starts with "\\" but  </span>
    <span style="background-color:rgb(255, 255, 255)">is not either
    "\\n" or "\\r\\n" then the following stack trace </span><span
    style="background-color:rgb(255, 255, 255)">is logged for every
    message processed by the adapter:          </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255,
    255)">com.ibm.j</span><span style="background-color:rgb(255,
    255, 255)">2ca.sap.exception.SapAleOutboundException
    </span><span style="background-color:rgb(255, 255, 255)">at
    com.ibm.j2ca.sap.ale.id</span><span
    style="background-color:rgb(255, 255,
    255)">oc.PassThroughIDoc.setDelimiter(PassThroughIDoc.java:288)
    </span><span style="background-color:rgb(255, 255, 255)">at
    com.ibm</span><span style="background-color:rgb(255, 255,
    255)">.j2ca.sap.ale.outbound.PassThroughAleInvoker.buildIdoc(Pas
    sThrou</span><span style="background-color:rgb(255, 255,
    255)">ghAleInvoker.java:153) </span><span
    style="background-color:rgb(255, 255, 255)">at
    com.ibm.j2ca.sap.ale.outbound.Pass</span>
    <span style="background-color:rgb(255, 255,
    255)">ThroughAleInvoker.postIdoc(PassThroughAleInvoker.java:89)<
    /span><span style="background-color:rgb(255, 255, 255)"> at
    com.ibm</span>
    <span style="background-color:rgb(255, 255,
    255)">.j2ca.sap.ale.outbound.AleInvoker.execute(AleInvoker.java:
    123) </span><span style="background-color:rgb(255, 255, 255)">at
    co</span>
    <span style="background-color:rgb(255, 255,
    255)">m.ibm.j2ca.sap.SAPInteraction.getOutputRecord(SAPInteracti
    on.jav</span><span style="background-color:rgb(255, 255,
    255)">a:284) </span><span style="background-color:rgb(255, 255,
    255)">at
    com.ibm.j2ca.sap.SAPInteraction.doExecute(SAPInteraction.j</span
    ><span style="background-color:rgb(255, 255, 255)">ava:118)
    </span><span style="background-color:rgb(255, 255, 255)"> at
    com.ibm.j2ca.base.WBIInteraction.execute(WBII</span><span
    style="background-color:rgb(255, 255, 255)">nteraction.java:522)
    </span><span style="background-color:rgb(255, 255, 255)">at
    com.ibm.broker.adapter.deploy.MbAd</span><span
    style="background-color:rgb(255, 255,
    255)">apterAccess.execute(MbAdapterAccess.java:188) </span><span
    style="background-color:rgb(255, 255, 255)"> at
    com.ibm.broker.adap</span><span style="background-color:rgb(255,
    255,
    255)">ter.nodes.MbAdapterRequestNode.requestData(MbAdapterReques
    tNode.</span><span style="background-color:rgb(255, 255,
    255)">java:589)</span><span style="background-color:rgb(255,
    255, 255)"> at
    com.ibm.broker.plugin.MbRequestTemplateNode.r</span><span
    style="background-color:rgb(255, 255,
    255)">equestData(MbRequestTemplateNode.java:60)</span><span
    style="background-color:rgb(255, 255, 255)">
                           </span>
    <span style="background-color:rgb(255, 255,
    255)">com.ibm.j2ca.sap.exception.SapAleOutboundException
         </span>
    <span style="background-color:rgb(255, 255, 255)">
                                                             </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">This can
    </span><span style="background-color:rgb(255, 255, 255)">flood
    the logs, especially on container based systems where the
    </span><span style="background-color:rgb(255, 255,
    255)">stdout/stderr streams are forwarded to a log consumer.
            </span>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT34080

  • 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

    2020-09-02

  • Closed date

    2020-12-17

  • Last modified date

    2020-12-17

  • 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

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

Document Information

Modified date:
12 January 2021