IBM Support

PI79302: JAVAX.EJB.TIMER#CANCEL DOESN'T WORK AS EXPECTED IF UNIQUETIMERMANAGERFORNP=TRUE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When we create IntervalTimer by calling
    TimerService.createIntervalTimer,
    the handleTimeout of the timer is executed periodically. And we
    expect that the current scheduled timer can be cancelled by
    calling timerService.getTimers and the following Timer.cancel
    method. But even after we call the cancel for the timer, the
    scheduled timer executes its handleTimeout if we select "Share
    thread pool configured for persistent timers" of "EJB timer
    service settings".
    

Local fix

  • uncheck "Share thread pool configured for persistent timers"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with non-persistent EJB timer        *
    *                  applications                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Non-persistent interval EJB timers may  *
    *                      expire and run one timer after being    *
    *                      cancelled                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After a non-persistent interval EJB timer expires and runs at
    least one time, then any attempt to cancel the timer will
    result in the timer still expiring and running one more time
    at the next scheduled interval after the cancel has completed.
    

Problem conclusion

  • The EJB container has been updated to ensure non-persistent
    interval EJB timers will not expire and run again after being
    cancelled.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.12.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI79302

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-03

  • Closed date

    2017-05-18

  • Last modified date

    2017-05-18

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022