Ok - so are we saying the default strategy will restart an actor that
throws an exception itself (seems to be the case) but a Kill affects it in
such a way that a custom strategy is needed? In this case doesn't that mean
that the kill is an inappropriate way of testing actor failures due to
excepti
Sending a Kill causes the actor to throw an ActorKilledException. By
default this leads to stopping the actor. You have to use a custom
supervisor strategy and restart the actor on a ActorKilledException.
Heiko
On Sun, May 11, 2014 at 9:44 PM, Tim Pigden wrote:
> Hi
> I tried getting rid of pr
Hi
I tried getting rid of previous "Bomb" message in favour of sending a Kill
This is on an event processor
The bomb method
case Bomb => throw new Exception("bombed my actor")
causes the EventProcessor to recover (I'm using default strategy)
Kill just kills it - with no recovery.
Have I mi
Thanks Tim, I'd kinda started down the (2) route.
On Wednesday, April 30, 2014 10:32:23 AM UTC-4, Tim Pigden wrote:
>
> Possible options might be:
> 1. register listeners on your eventsourcedProcessor and send them the
> events.
> 2. use an eventbus to publish the events (saves mucking around m
Possible options might be:
1. register listeners on your eventsourcedProcessor and send them the
events.
2. use an eventbus to publish the events (saves mucking around managing
listeners explicitly)
3. subclass and return events to sender
On 30 April 2014 14:28, erich oliphant wrote:
> THanks
THanks guys,I'd gotten the in-mem journal etc. working, my question was
more around say verifying emitted/journaled events. If i send in a
CreateOrder to my 'OrderEventsourcedProcessor' how do I do something like
an 'expectMsg(OrderCreated)' or is this the correct approach?
On Wednesday, April
We have a full example as part of the akka persistence mongo journal here:
https://github.com/ddevore/akka-persistence-mongo/tree/master/akka-persistence-mongo-command-sourcing-example-app
Note: This is command sourcing only and we are about to do a full sample
with event sourcing and views.
O
Hi Erich,
As Tim pointed out, one way is to use an in-memory journal and use the
ordinary akka TestKit. To simulate failures you may use the Kill message (
http://doc.akka.io/docs/akka/2.3.2/scala/actors.html#Killing_an_Actor) that
will force the actor to throw an ActorKilledException. It might be
I don't know if this answers your question but this is what I did:
I just used a normal specs2 test with TestKit
In order to test full cycle I used
"com.github.michaelpisula" %% "akka-persistence-inmemory" %
"0.1-SNAPSHOT" % "test"
which requires
akka.persistence.journal.plugin = "akka.pers
