Hi Jasper
I faced a similar problem just before my vacation (Naughty database that
might block in circuit breakers). I'm just an akka newbie but for what's it
worth here's what I did. I found that using withSyncCircuitBreaker in these
cases was a bad idea. I solved my problem by making the
Would it be allright if I placed a ticket on this functionality (scheduling
for ActorSelections in much the same way as ActorRefs)?
Best Regards
Måns Schultz
2014-07-07 12:55 GMT+02:00 Heiko Seeberger hseeber...@posteo.de:
On 07 Jul 2014, at 12:29, Måns Schultz gfae...@gmail.com wrote
Cool! Can do. :-)
2014-07-11 16:04 GMT+02:00 Martynas Mickevičius
martynas.mickevic...@typesafe.com:
Yes. Even better, if you did a PR. :)
On Fri, Jul 11, 2014 at 2:07 PM, Måns Schultz gfae...@gmail.com wrote:
Would it be allright if I placed a ticket on this functionality
method has a stop condition
(receiver.isTerminated) which I guess would be hard to replicate for
selections.
All this can ofcourse be accomplished using anonymous Runnables, would just
be nice to avoid it if there are no outstanding issues.
Best Regards
Måns Schultz
--
Read the docs
Thanks for the reply!
Thanks for the correction about stale ActorRefs. But the statement holds
true if I kill the actor and replace it with something else on the same
path right? (like switching a service at runtime).
Best Regards
Måns Schultz
2014-07-07 12:16 GMT+02:00 Heiko Seeberger
. Please create
an issue https://github.com/akka/akka/issues and if you are interested
in contributing a pull request would be awesome.
and, yes, the future must be created inside the Callable call.
Regards,
Patrik
On Wed, Jul 2, 2014 at 1:57 PM, Måns Schultz gfae...@gmail.com wrote:
Hello
Regards
Måns Schultz
--
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
