IBM Support

PK95800: INFINITY LOOPING OF EJB TIMER CAUSES RUNNING OUT OF DATABASE CONNECTION

 

APAR status

  • Closed as program error.

Error description

  • The removeTimer() method called a contains() which creates a
    infinity loop until runs out the database connection, customer
    will see following repeat exception:
    
    
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.getTim
    erFromPersistenceStore(EJBSchedulerBean.java:1044)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.findSc
    hedulables(EJBSchedulerBean.java:316)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJSRemoteStatelessEJBSc
    heduler_27162c8e.findSchedulables(Unknown Source)
    
    com.ibm.workplace.wcm.util.scheduler.ejb._EJBScheduler_Stub.find
    Schedulables(_EJBScheduler_Stub.java:317)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:186)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:132)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:127)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.contains(SchedulerServiceImpl.java:296)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.TimerDatabase.removeTim
    er(TimerDatabase.java:426)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.getTim
    erFromPersistenceStore(EJBSchedulerBean.java:1056)
    

Local fix

Problem summary

  • Infinity caused running out database connection
    
    The following stacktrace shows there is a coding loop, each
    getTimerFromPersistenceStore() method requires a database
    connection, this matches the theory that the same thread open
    all connections in a short time.
    
    the following is the reported stack:
    
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.getTim
    erFromPersistenceStore(EJBSchedulerBean.java:1044)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.findSc
    hedulables(EJBSchedulerBean.java:316)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJSRemoteStatelessEJBSc
    heduler_27162c8e.findSchedulables(Unknown Source)
    
    com.ibm.workplace.wcm.util.scheduler.ejb._EJBScheduler_Stub.find
    Schedulables(_EJBScheduler_Stub.java:317)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:186)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:132)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.findSchedulables(SchedulerServiceImpl.java:127)
    
    com.ibm.workplace.wcm.util.scheduler.service.SchedulerServiceImp
    l.contains(SchedulerServiceImpl.java:296)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.TimerDatabase.removeTim
    er(TimerDatabase.java:426)
    
    com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedulerBean.getTim
    erFromPersistenceStore(EJBSchedulerBean.java:1056)
    

Problem conclusion

  • Fixed the loop problem to avoid the problem
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK95800

  • Reported component name

    LOTUS WEB CONT

  • Reported component ID

    5724I2900

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-09-09

  • Closed date

    2009-09-10

  • Last modified date

    2009-09-10

  • 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 WEB CONT

  • Fixed component ID

    5724I2900

Applicable component levels

  • R61A PSY

       UP

[{"Business Unit":{"code":"BU051","label":"N\/A"},"Product":{"code":"SUPPORT","label":"IBM Web Content Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Line of Business":{"code":"LOB33","label":"N\/A"}}]

Document Information

Modified date:
21 December 2021