Hello,

we have a Play application which sends remote messages to another component 
and sometimes without any apparent reason gives a timeout error.
The remote message uses the ask-pattern and the returned Future times out, 
as follows:

play.api.Application$$anon$1: Execution exception[[TimeoutException: 
Futures timed out after [15000 milliseconds]]]
  at play.api.Application$class.handleError(Application.scala:287) 
~[play_2.10-2.1.5.jar:2.1.5]
  at play.api.DefaultApplication.handleError(Application.scala:381) 
[play_2.10-2.1.5.jar:2.1.5]
  at 
play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$18$$anonfun$apply$18.apply(PlayDefaultUpstreamHandler.scala:312)
 
[play_2.10-2.1.5.jar:2.1.5]
  at 
play.core.server.netty.PlayDefaultUpstreamHandler$$anonfun$18$$anonfun$apply$18.apply(PlayDefaultUpstreamHandler.scala:310)
 
[play_2.10-2.1.5.jar:2.1.5]
  at 
play.api.libs.concurrent.PlayPromise$$anonfun$extend1$1.apply(Promise.scala:113)
 
[play_2.10-2.1.5.jar:2.1.5]
  at 
play.api.libs.concurrent.PlayPromise$$anonfun$extend1$1.apply(Promise.scala:113)
 
[play_2.10-2.1.5.jar:2.1.5]
  at 
play.api.libs.concurrent.PlayPromise$$anonfun$extend$1$$anonfun$apply$1.apply(Promise.scala:104)
 
[play_2.10-2.1.5.jar:2.1.5]
  at 
scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
 
[scala-library.jar:na]
  at 
scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24) 
[scala-library.jar:na]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 
[na:1.6.0_31]
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[na:1.6.0_31]
  at java.lang.Thread.run(Thread.java:662) [na:1.6.0_31]
java.util.concurrent.TimeoutException: Futures timed out after [15000 
milliseconds]
  at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:96) 
~[scala-library.jar:na]
  at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:100) 
~[scala-library.jar:na]
  at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107) 
~[scala-library.jar:na]
  at 
akka.dispatch.MonitorableThreadFactory$AkkaForkJoinWorkerThread$$anon$3.block(ThreadPoolBuilder.scala:169)
 
~[akka-actor_2.10-2.2.4.jar:2.2.4]
  at 
scala.concurrent.forkjoin.ForkJoinPool.managedBlock(ForkJoinPool.java:2803) 
~[scala-library.jar:na]
  at 
akka.dispatch.MonitorableThreadFactory$AkkaForkJoinWorkerThread.blockOn(ThreadPoolBuilder.scala:167)
 
~[akka-actor_2.10-2.2.4.jar:2.2.4]
  at scala.concurrent.Await$.result(package.scala:107) 
~[scala-library.jar:na]

On the server side, nothing is shown in the logs and the component is fine 
as just restarting the Play app solves the problem.
Given that we are not able to reproduce the error, has anybody any idea on 
what could be causing such issue or any advice on what we could investigate 
to have more clues (any log to switch on, configuration setting, ...)
We use Scala 2.10.0, Play 2.1.5 and Akka 2.2.4.

Thank you very much in advance

Giovanni Ruggiero

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to