Re: [akka-user] Is there any reason(s) why Await inside an Actor would be different in (Play's) Development mode versus Production mode?

Blocking inside a lazy val initializer is most definitely very discouraged. Instead make it a lazy val to a Future[T]. On Thu, Jun 9, 2016 at 11:43 AM, Akka Team wrote: > Hi Gary, > > Can it be that the number of blocking calls (calls to Await.result) cause > all threads in the pool to block, he

Re: [akka-user] Is there any reason(s) why Await inside an Actor would be different in (Play's) Development mode versus Production mode?

Hi Gary, Can it be that the number of blocking calls (calls to Await.result) cause all threads in the pool to block, hence unable to fulfill some asynchronous task that is needed by the Await itself, and deadlock the system? Also, I am not sure how lazy val initialization is implemented, but I th

[akka-user] Is there any reason(s) why Await inside an Actor would be different in (Play's) Development mode versus Production mode?

I have the following use case: I need to get a token via an initial Remote API web call and then use that token for all subsequent API calls. Simple enough. Here is the chunk of code however that simply STOPS (stalls) working in production: lazy val authTokenPairJSON: play.api.libs.json.J