IBM Support

JR57084: YOU RECEIVE ERROR SCHD0128E: THE DAEMON FOR SCHEDULER APPSCHEDULER COULD NOT BE STARTED DURING SERVER STARTUP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • An error similar to the following error is logged in the
    SystemOut.log file when the application server starts:
    
    [11/16/16 12:13:14:156 EST] 0000007f SchedulerServ E
    SCHD0128E: The daemon for scheduler AppScheduler could not be
    started:
    com.ibm.ws.scheduler.exception.SchedulerDataStoreException:
    SCHD0124E: Unable to initialize TaskStore due to error:
    SCHD0046E: The table SCHEMA..WSCH_TREG in datasource jdbc/WPSDB
    used by scheduler resource AppScheduler (AppScheduler) is
    missing or is not accessible.
     at
    com.ibm.ws.scheduler.SchedulerImpl$9.run(SchedulerImpl.java:2517
    )
     at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:453)
     at
    com.ibm.ws.scheduler.SchedulerImpl.startDaemon(SchedulerImpl.jav
    a:2477)
     at
    com.ibm.ws.scheduler.SchedulerServiceImpl.autoStartDaemon(Schedu
    lerServiceImpl.java:885)
     at
    com.ibm.ws.scheduler.SchedulerServiceImpl.startSchedulers(Schedu
    lerServiceImpl.java:828)
     at
    com.ibm.ws.scheduler.SchedulerServiceImpl.access$300(SchedulerSe
    rviceImpl.java:126)
     at
    com.ibm.ws.scheduler.SchedulerServiceImpl$DaemonStarter.run(Sche
    dulerServiceImpl.java:1317)
     at
    com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializ
    er.run(WsComponentImpl.java:502)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    

Local fix

  • Change the data sources in the property file to be listed under
    the correct database. Do not change the property names of data
    sources in an exported property file.
    

Problem summary

  • It was possible to create an IBM BPM deployment environment by
    using a property file where the data sources are defined under a
    wrong database object. When this occurs, the data sources are
    created in the wrong scope, for example, the cell-level
    jdbc/WPSDB data source might be created on the application
    cluster. As a result, you receive various errors when the
    database is accessed by the IBM BPM runtime code.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR57084

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-29

  • Closed date

    2016-12-07

  • Last modified date

    2016-12-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R856 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 December 2016