Hi Raul, Please use the following link to track the issue: https://issues.apache.org/jira/browse/IGNITE-5773
Thanks, Mikhail. On Sun, Jul 16, 2017 at 6:14 PM, Raul <[email protected]> wrote: > Hi, > > Any update on the issue? > > On 11 July 2017 at 16:01, chapurlatn <[email protected]> wrote: > >> Sorry if the message appears twice. >> I figured out my account was not ready to post when I send my first >> message >> : >> >> Hi, >> >> I think the scheduler processor does not match the expected processor >> interface. This results to a bad state. >> >> IgniteKernal is responsible to start each processors : >> org.apache.ignite.internal.IgniteKernal.startProcessor(GridProcessor): >> proc.start(cfg.isActiveOnStart()); >> >> But the >> org.apache.ignite.internal.processors.schedule.IgniteScheduleProcessor >> does >> not implement it (missing boolean parameter) : >> >> /** {@inheritDoc} */ >> @Override public void start() throws IgniteCheckedException { >> sched = new Scheduler(); >> sched.start(); >> } >> >> That's why the default (empty) impl is used. And the "sched" attribute >> stay >> null. >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Scheduler-throwing-NullPointerException-for >> -Ignite-2-0-0-tp13420p14637.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > > -- Thanks, Mikhail.
