I want one of my actors to deal with some 'MarketUpdate messages. Since I
only care about the latest/last message received, I'd like my actor to
discard all pending messages in its mailbox except the last one. Shall I
just use a bounded mailbox and set its mailbox-capacity to 1. Will that
Say I have several persistent view actors of the same type in a cluster,
and one of them is just up and busy recovering its in-memory state.
Assume I have a cluster-aware routing that routes messages to those actors,
how shall I avoid messages being sent to the one actor in the recovering
Hi,
I am new in Akka.
Here's situation.
I am writing program which computes some math problem.
1 Experiment is computed by 1 EvaluationActor
No. of experiments might be thousands,or hundreds of thousends, even more.
Each EvaluationActor has child actor - ResultActor which collects stats
from
Hi guys,
I'm writing up some examples for persistence and stumbled on a strange
issue.
Can you please have a look at this? The gist contains a unit test you can
drop straight into akka-persistence to verify it.
https://gist.github.com/RayRoestenburg/9580479
I used to use ImplicitSender in the
Please disregard, I misunderstood and found out why.
The replayed message causes the response back to the probe.
On Sunday, March 16, 2014 10:17:08 AM UTC+1, Raymond Roestenburg wrote:
Hi guys,
I'm writing up some examples for persistence and stumbled on a strange
issue.
Can you please
Ok, I've got another question.. I've expanded the gist:
https://gist.github.com/RayRoestenburg/9581923
I've added a channel to respond to clients to the NumberProcessor example,
(NumberProcessorWithChannel) and I see something unexpected again, which
might be me learning how this really works,
Ok you can also ignore this one,
(this is a fantastic rubber ducking session by the way! ;-P)
When I create the channel outside of the processor and reuse that,
everything works as expected:
https://gist.github.com/RayRoestenburg/9582319
Of course every new child channel cannot know which
In retrospect, having JavaSerializer was probably a mistake.
On Mar 16, 2014 1:17 PM, Carsten Saathoff cars...@kreuzverweis.com
wrote:
Am Sonntag, 16. März 2014 03:50:49 UTC+1 schrieb Daniel Wang:
I'm also very interested in your benchmark result. Carsten, please share
more data when they are
Ok, I was abkle to found the problem, there is nothing to do with akka.
it is a scala issue, that is supossed to be fixed on scala 2.11 :)
I was able to make a work around using a object with a synchronized method,
so only thread access the reflection method.
Thanks
Here is the issue ticket
Hi Daniel,
On Sun, Mar 16, 2014 at 4:04 AM, Daniel Wang dan...@coinport.com wrote:
Say I have several persistent view actors of the same type in a cluster,
and one of them is just up and busy recovering its in-memory state.
Assume I have a cluster-aware routing that routes messages to those
10 matches
Mail list logo
