Hi Roland, sorry for the delay:
On Tuesday, May 13, 2014 9:11:58 AM UTC+2, rkuhn wrote: > > Hi Giovanni, > > 13 maj 2014 kl. 08:49 skrev Giovanni Ruggiero > <giovanni...@eligotech.com<javascript:> > >: > > On Saturday, May 10, 2014 3:30:42 PM UTC+2, rkuhn wrote: > >> >> 10 maj 2014 kl. 10:35 skrev Giovanni Ruggiero >> <giovanni...@eligotech.<http://eligotech.com/> >> com <http://eligotech.com/>>: >> >> >> What puzzles us is that the ask() message gets responded. It's the >> returned Future that times out. >> >> >> If the Future times out, then the reason for that is that no reply was >> sent within the timeout window. Are you sending to the right ActorRef? >> > > Yes, as the same actor responds fine until the error appears. > >> >> Another strange thing is that after the first time out, all following >> requests fail in the same manner. >> >> >> Are you using a CircuitBreaker? >> > > > No, we don't have any CircuitBreaker. > > Does your actor block or get stuck? >> > > The server actor still works, because just restarting the client Play app > solves the problem. > The client app just returns the future time out, so I'm not sure how to > respond to your question. > > > Ah, this opens up new possibilities: if the actor actually responds (and > sends the response to the right ActorRef), but the Future still times out, > then that means that the message has been lost. You mention that this ask() > crosses application boundaries, which I assume implies that remoting is > used, and there it is entirely possible that the connection fails. When the > failure detector triggers and the systems quarantine each other then no > further communication will be possible (until you restart one of the > systems). > > Yes we use remoting, but both components are on the same physical server, just two different JVM. > Which version of Play and Akka are you using? What are the configuration > settings? Which kind of network is connecting the client and server apps? > Do you use DeathWatch or create actors across the network connection? > Please also scrutinize the logs, if my guess is correct you will find error > messages from the remoting. > > We use Scala 2.10.0, Play 2.1.5 and Akka 2.2.4, but we are going to upgrade to the last versions soon. What kind of configuration are you referring? Here is an excerpt of our configuration file: harpoon { actor-system { akka { loggers=["akka.event.slf4j.Slf4jLogger"] loglevel=DEBUG stdout-loglevel=DEBUG remote { netty.tcp { transport-protocol=tcp hostname=${harpoon.application.services-host} connection-timeout=120 seconds all-timeout=120 seconds } } actor { provider="akka.remote.RemoteActorRefProvider" serialize-messages=on } } jobmanager { actor-system { akka { actor { debug { receive=on autoreceive=on lifecycle=on } remote.netty.tcp.port = 9303 } } } } weblayer { actor-system { akka { remote.netty.tcp.port = 9302 } } services { jobService = "akka.tcp://JobManagerService@"${harpoon.application.services-host}":9303/user/jobService" } } } The logs in the "weblayer" component show the Future timeout. The logs in the "jobmanager" component show nothing at all. Thank you Giovanni Regards, > > Roland > > > The problem is that this seldom happens. For example, it hasn't showed > from the start of this thread. > > Thank you > > Giovanni > > Regards, > > Roland > > > Thanks > > Giovanni > > On Thursday, May 8, 2014 11:07:06 PM UTC+2, Akka Team wrote: >> >> Sometimes things take time, and somethings messages can also be lost >> (Akka does at-most-once delivery), so an ask() timing out is something that >> you will need to expect and handle, even if it should happen rarely. >> >> Regards, >> >> Roland >> >> >> >> On Thu, May 8, 2014 at 3:08 PM, Giovanni Ruggiero <giovanni...@ >> eligotech.com> wrote: >> >>> >>> No, this happens with several actors, not related to db connections. >>> One thing we have observed is that happens after the Play application >>> has been idle for a long period. >>> >>> Thanks >>> Giovanni >>> >>> >>> On Thursday, May 8, 2014 12:25:47 AM UTC+2, Muki wrote: >>>> >>>> Hi, >>>> >>>> I have similar problems with play. The error appears very rarely, which >>>> makes it hard to track. >>>> Do you build a database connection inside your actor? >>>> >>>> Cheers, >>>> Muki >>>> >>>> >>> -- >>> >>>>>>>>>> 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 akka-user+...@googlegroups.com. >>> To post to this group, send email to akka...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/akka-user. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Akka Team >> Typesafe - The software stack for applications that scale >> Blog: letitcrash.com >> Twitter: @akkateam >> > > -- > >>>>>>>>>> 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 akka-user+...@googlegroups.com. > To post to this group, send email to akka...@googlegroups.com. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > > >> >> >> *Dr. Roland Kuhn* >> *Akka Tech Lead* >> Typesafe <http://typesafe.com/> – Reactive apps on the JVM. >> twitter: @rolandkuhn >> <http://twitter.com/#!/rolandkuhn> >> >> > -- > >>>>>>>>>> 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 akka-user+...@googlegroups.com <javascript:>. > To post to this group, send email to akka...@googlegroups.com<javascript:> > . > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > > > > > *Dr. Roland Kuhn* > *Akka Tech Lead* > Typesafe <http://typesafe.com/> – Reactive apps on the JVM. > twitter: @rolandkuhn > <http://twitter.com/#!/rolandkuhn> > > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
