IBM Support

LO88065: OUT OF MEMORY ERRORS CAUSED BY A CLIENT SENDING EMAIL TO A LIST OF ADDRESSES WHERE A NON-FIRST ADDRESS WAS 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

  • An infinite loop while processing certain valid and invalid
    email addresses in a mail sent from the client could cause the
    Traveler server to run out of memory.  This is very rare and
    requires a specific set of valid and invalid addresses to be
    used.  The client was sending a mail with multiple addresses in
    the CC field (it could be the To filed too).  At least the first
     address was valid and at least one non-first address was
    invalid.  Traveler has 3 different ways to try to handle the
    address as a valid address.  The invalid address had to be
    considered valid by the first check and invalid by the second
    check; if the first check failed, you could not hit this error
    condition.  When the second check encountered the invalid
    address, it had already put the previous address in the list to
    be checked individually, so when the third check put all of the
    address in the list to be checked individually, too many got
    added (as the already handled ones got added twice) and the
    checking never got to the end of the list as it just continued
    to grow.  This list checking continued until the server ran out
    of Java memory in the Traveler (not HTTP) process.
    

Local fix

  • Have the user stop sending that mail by removing it from the
    client or banning the user from the server.
    

Problem summary

  • String processing error when the recipient list contains invalid
    characters for e-mail addresses.
    

Problem conclusion

  • The IBM Traveler server was update to handle this scenario
    correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO88065

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-20

  • Closed date

    2016-03-08

  • Last modified date

    2016-03-08

  • 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

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO88065

Modified date: 08 March 2016