milap.wadhwa On 15 July 2016 at 11:36, Denis Magda <[email protected]> wrote:
> Hi, > > What is your Apache Ignite JIRA account? > > — > Denis > > > On Jul 14, 2016, at 7:37 PM, Milap Wadhwa <[email protected]> > wrote: > > > > Hi, > > > > I would like to pick up this ticket. Please assign me this ticket. > > > > > > Thanks, > > Milap Wadhwa > > > > On 2 February 2016 at 10:50, Valentin Kulichenko (JIRA) <[email protected] > > > > wrote: > > > >> Valentin Kulichenko created IGNITE-2527: > >> ------------------------------------------- > >> > >> Summary: 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.6 > >> > >> > >> 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) > >> > >
