IBM Support

IJ48875: EMAIL LISTENER FAILED TO CREATE STAGING TABLE RECORD

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

  • ERROR DESCRIPTION:
    Email Listener Failed to create staging table record
    
    PROBLEM:
    Email listener will not update staging table if an email is sent
    with an attachment that has a type of .msg.
    This happens only when emailing from a Windows Operating System
    computer from the Outlook application.
    It also only appears to be happening in Maximo 7.6.1.3
    environments. This was not an issue on Maximo 7.6.1.2.
    
    The following error was found in the log:
    
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O Failed to create
    staging table record for e-mail address support-trn@emaximo.com
    and mail server outlook.office365.com . Please review the Maximo
    log file for more details.
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O Incoming e-mail
    details - Sender E-mail Address: ahenle@projetech.com, Subject:
    IBM Case Test, Receive Date: 7/18/23 10:27 AM.
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O
    java.lang.NullPointerException
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.util.St
    ringUtility.removePercentSigns(StringUtility.java456)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.common.
    emailstner.EmailListnerTask.writeToDocInfoAndDocLinks(Emai
    lListnerTask.java2295)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.common.
    emailstner.EmailListnerTask.writeIntoInboundComm(EmailList
    nerTask.java2210)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.common.
    emailstner.EmailListnerTask.readMessagesFromMailServer(Ema
    ilListnerTask.java880)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.common.
    emailstner.EmailListnerTask.performTask(EmailListnerTask.j
    ava266)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.common.
    emailstner.EmailListnerCron.cronAction(EmailListnerCron.ja
    va49)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.server.
    CronTaskManager.callCronMethod(CronTaskManager.java2594&#04
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.server.
    CronTaskManager.access$1100(CronTaskManager.java107)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at psdi.server.
    CronTaskManager$CronThread.run(CronTaskManager.java3512&#04
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at java.util.co
    ncurrent.Executors$RunnableAdapter.call(Executors.java522&#
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at
    java.util.concurrent.FutureTask.run(FutureTask.java
    277)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at java.util.co
    ncurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access
    $201(ScheduledThreadPoolExecutor.java191)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at java.util.co
    ncurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run&#0
    40;ScheduledThreadPoolExecutor.java304)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at java.util.co
    ncurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
    ava1160)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at java.util.co
    ncurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
    java635)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O at
    java.lang.Thread.run(Thread.java 825)
    [7/18/23 10:27:30:918 EDT] 000001a0 SystemOut O
    ------=_Part_4_-1768887509.1689690450887--
    
    The first reference after the NullPointer error indicates
    "RemovePercentSigns", so we wonder if percentages are not
    recognized by Maximo.
    
    
    STEPS TO REPRODUCE:
    Create email listener and try to send a email to it with a .MSG
    file attached having symbols like percentage in the content.
    Your email will not be processed.
    Errors will be seen in the logs.
    
    CURRENT ERRONEOUS RESULT:
    The email does not update the staging table in Maximo. So it
    does not create/update the record it should.
    
    EXPECTED RESULT:
    The email sends to the listener and creates/updates an SR as the
    email listener is set up.
    
    ENVIRONMENT (SYSTEM INFO):
    IBM WebSphere Application Server 9.0.5.15
    Tivoli's process automation engine 7.6.1.3-IFIX20230424-1648
    Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-76
    IBM Maximo Application Framework 8.8.0 Build 20220823-1257 DB
    Build V7600-23
    IBM Tpae Integration Framework 7.6.1.3 Build 20220823-0909 DB
    Build V7613-61
    IBM Maximo for Service Providers 7.6.3.4-20230317-1510 Build
    20230317-1510 DB Build V7634-10 HFDB Build HF7634-16
    IBM Maximo Asset Management 7.6.1.3 Build 20220823-0909 DB Build
    V7611-01
    IoT Connection Utility 7.6.0.4 Build 20220303-1642 DB Build
    V7604-01
    IBM Maximo Health, Safety and Environment Manager
    7.6.2.0-20220822-1033 Build 20220822-1033 DB Build V7620-02
    Server OS Windows Server 2016 10.0
    Server DB Microsoft SQL Server 13.0 (13.00.6300)
    (c) Copyright IBM Corp. 2021
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    Email listener customers using RFC822 email server functionality
    encounter null pointer.
    

Problem conclusion

  • The fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ48875

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-10-11

  • Closed date

    2023-12-12

  • Last modified date

    2023-12-12

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
12 December 2023