If I'm not mistaken then this was a limitation of Akka's ask futures. The maximum timeout was as specified. It might have changed with a new version, though. Usually, you should rarely run into a case where this actually matters.
Cheers, Till On Mon, Aug 29, 2016 at 5:44 PM, Greg Hogan <c...@greghogan.com> wrote: > Could be rewritten as "val INFO_TIMEOUT = Integer.MAX_VALUE seconds"? > > On Mon, Aug 29, 2016 at 4:22 AM, 时金魁 <shijinkui...@163.com> wrote: > > > > > > > AkkaUtils.scala > > val INF_TIMEOUT = 21474835 seconds > > > > > > That is job submit timeout 248.55 days. > > > > > > Why is this number? > > > > > > > > >
