IBM Support

IT25540: JAVA NULLPOINTEREXCEPTION IN EMAILOUTPUT NODE WHEN USING MULTIPLE FROM ADDRESSES

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

  • If multiple 'From' addresses are specified in the
    EmailOutputHeader sent to an EmailOutput node then a Java
    NullPointerException is thrown from
    InternetAddress.java:toString.
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s):EMAILOUTPUT header,
    EmailOutput node, Java NullPointerException, MULTIPLE ADDRESSES
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 and IBM App Connect
    Enterprise v11 who use the the EmailOutput node.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an EmailOutput node receives a message where there are
    multiple email addresses listed in Root.EmailOutputHeader.From
    field then a Java NullPointerException will be thrown.
    Additionally, the RFC that defines the email format, RFC 2822,
    states that the header 'Sender' must be present when multiple
    addresses are listed in the 'From' header. Currently the product
    does not check for the existence of the Sender header, nor does
    it validate that it is a valid email address. Finally, the
    documentation for the EmailOutput node and the page entitled
    "Producing dynamic email messages" do not detail the existence
    of the Sender header, or the fact that custom header fields can
    be set in the EmailOutputHeader.
    

Problem conclusion

  • The product will no longer throw the NullPointerException when
    using multiple 'From' addresses. The product will also validate
    that the Sender header has been set if multiple 'From' addresses
    are used, and that the specified value is a valid email address.
    The documentation for the EmailOutput node and the page entitled
    "Producing dynamic email messages" has been updated to reflect
    the existence of the 'Sender' header, and that custom headers
    can be specified.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.14
    v11.0      11.0.0.2
    
    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

    IT25540

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-29

  • Closed date

    2018-09-26

  • Last modified date

    2018-09-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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
26 September 2018