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.70518.x6.nabble.com/Scheduler-throwing-NullPointerException-for-Ignite-2-0-0-tp13420p14635.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
