Hi ronly2008,
I applied your stacktrace on ignite-2.0.0, but code lines is does not
matched. Are you sure that you use ignite-2.0.0 (it is tag)? Can you provide
small reproducer? It can help solve problem more quickly.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble
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 wrote:
> Hi,
>
> Any update on the issue?
>
> On 11 July 2017 at 16:01, chapurlatn wrote:
>
>> Sorry if the message appears twice
Hi,
Any update on the issue?
On 11 July 2017 at 16:01, chapurlatn 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 re
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.ig
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
Adding those line of code just after the startup solved the pb (very
temporarily).
ignite = Ignition.start(conf);
if (ignite instanceof IgniteKernal) {
IgniteScheduleProcessorAdapter scheduler = ((IgniteKernal)
ignite).context().schedule();
if (scheduler instanceof IgniteScheduleProcessor
Hi Alexey,
This exception occurs right on start up as we try to add our services to
the cron.
We are using the scheduler as an example given your docs (
https://apacheignite.readme.io/docs/cron-based-scheduling).
Below is the example, similar to the issue raised by another user, link for
the ref
Hi Raul,
Do you observe this exception under some specific events, like topology
change? Can you share an example of how you use Ignite scheduler in your
service here?
Thanks,
AG
2017-06-06 17:21 GMT+03:00 Raul :
> Hi,
>
> We are trying to deploy a service as cluster singleton in our environmen
Hi,
We are trying to deploy a service as cluster singleton in our environment.
We are using ignite scheduler as a cron for this purpose, however we are
getting NPE for ignite version 2.0.0, hence unable to proceed with our
version upgrade. Below is the log information for the exception.
Environme
