Take a look at this discussion:
https://groups.google.com/d/msg/akka-user/a8GcX2qEm6g/OIbFTtPaSRoJ
/Patrik
On Tue, Sep 30, 2014 at 9:48 PM, Daniel Davies davi...@att.net wrote:
Thanks for the hint. I had trouble getting the router and children to use
a different dispatcher. However, I was
Hi Mike,
Did you look at the distributed worker pattern ?
See: http://typesafe.com/activator/template/akka-distributed-workers
That may be a better match looking at your use case.
Kind regards,
Olger
On Tuesday, September 30, 2014 11:41:59 PM UTC+2, Michael Kohout wrote:
Hi Folks-
1 okt 2014 kl. 03:45 skrev Richard Rodseth rrods...@gmail.com:
Thanks, Konrad. I have a little test working, but I'm puzzled by one thing.
If all I want to do is subscribe to individual channel ids (Longs, not
Strings), the SubChannelClassification doesn't seem appropriate. But the
Hi Richard,
No, I mean the other complete() method that you call from the Success and
Failure paths of the onComplete block. Why not just use
complete(result.transform(...))?
-Endre
On Wed, Oct 1, 2014 at 2:01 AM, Richard Rodseth rrods...@gmail.com wrote:
Hi Endre
Yes, the one I showed
Hi Sean,
On Wed, Oct 1, 2014 at 6:40 AM, Sean Zhong clock...@gmail.com wrote:
The hierachy may looks like this:
grandpa - parent - child
When I restart grandpa(grandpa throws a exception, and its supervisor
handle with Restart), I want the whole tree is restarted.
parent actor and
hi all,
my understanding is that when I have:
actorRef ? hi
and the future times out, the reply eventually sent back from actorRef goes
to dead-letters.
That is fine but the log is polluted with messages about dead letters
encountered related to those replies.
Is there a way to filter out
Hi,
If anyone has any ideas/suggestions regarding the above issue, that would
be great. I can share my test code if it will help.
Unfortunately in these kind of integration tests sometimes long timeouts
are needed. It is btw good to be aware of these since these timing issues
are relevant in
Hi Jonas
Thanks a lot to take the time to answer such question, I really appreciate!
I'm a bit surprised though: most of the books/papers you refer are
research level, meaning for building solutions. I was kind of
thinking/hoping some solutions would already be built
On Tue, Sep 30, 2014 at
Hi Christian,
just saw that the SelectedSnapshot issue seems to be related to the
akka.persistence casbah mongodb plugin and was fixed a few days ago. I also
had a look again at the snapshot serializer and saw this:
val header = SnapshotHeader(snapshotSerializer.identifier,
Sure, but Björn pointed out above that doing it this way prevents me from
scaling out to multiple servers. If the end goal is to have at least the
leaf nodes of the tree be processed in a distributed manner (in a pool
across multiple servers), what's the best way to achieve that?
On Tuesday,
Excellent.. Thanks.
On Wed, Oct 1, 2014 at 1:00 AM, Roland Kuhn goo...@rkuhn.info wrote:
1 okt 2014 kl. 03:45 skrev Richard Rodseth rrods...@gmail.com:
Thanks, Konrad. I have a little test working, but I'm puzzled by one
thing. If all I want to do is subscribe to individual channel ids
Thanks for clarifying. I was using the version of complete I showed in
order to have control over the status code etc, but there are no doubt
other ways to do that in Spray.
My takeaway is that I shouldn't be too hasty about standardizing on
per-request actors.
On Wed, Oct 1, 2014 at 2:13 AM,
This looks interesting. Future.collect. Learn something new every day.
http://www.superloopy.io/articles/2013/spray-routing-error-handling.html
On Wed, Oct 1, 2014 at 11:00 AM, Richard Rodseth rrods...@gmail.com wrote:
Thanks for clarifying. I was using the version of complete I showed in
How to drain daemon system actors' queues on system exit?
--
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
Dear all,
When running our Akka cluster in docker we need to bind netty to 0.0.0.0 to
make it accessible to the outside of the container and binding to the external
ip of the docker host is not possible. However, the seed node uri needs to
point to the external ip in order to connect to the
I must clarify saying draining I mean giving to all system's actors some
duration to process all already sent messages.
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives:
Hello Andrew,
you might find “the Reaper” pattern of interest to you:
http://letitcrash.com/post/30165507578/shutdown-patterns-in-akka-2
--
Konrad 'ktoso' Malawski
hAkker @ typesafe
http://akka.io
--
Read the docs: http://akka.io/docs/
Check the FAQ:
Konrad, great, thanks! - will dig in...
--
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
18 matches
Mail list logo