You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Milap Wadhwa (JIRA)" <ji...@apache.org> on 2016/07/14 15:08:20 UTC

[jira] [Commented] (IGNITE-2527) IndexOutOfBoundsException in scheduler future

    [ https://issues.apache.org/jira/browse/IGNITE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377086#comment-15377086 ] 

Milap Wadhwa commented on IGNITE-2527:
--------------------------------------

Hi All,

I would like to pick up this ticket. Please assign me this ticket.


Thanks
Milap Wadhwa

> IndexOutOfBoundsException in scheduler future
> ---------------------------------------------
>
>                 Key: IGNITE-2527
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2527
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Valentin Kulichenko
>            Priority: Minor
>             Fix For: 1.7
>
>
> Calling {{SchedulerFuture.nextExecutionTime()}} (and probably other methods) on a completed future leads to this exception:
> {noformat}
> Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0
> 	at org.apache.ignite.internal.processors.schedule.ScheduleFutureImpl.nextExecutionTime(ScheduleFutureImpl.java:455)
> {noformat}
> In particular, this happens if {{nextExecutionTime()}} right after calling {{IgniteScheduler.scheduleLocal()}} with an invalid pattern (see code example below). The exception is lost in this case and is never printed out or thrown.
> {code}
> SchedulerFuture schedulerFuture = ignite.scheduler().scheduleLocal(() -> {}, "{55} 53 3/5 * * *");
> long nextExecutionTime = schedulerFuture.nextExecutionTime();
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)