Hello Tim!
The PersistentActor is not the guy with the lock, it’s the (LevelDB)
journal.
You only need 1 actor system running (and one journal) to test what you
want, example:
class MyPersistentActor(override val persistenceId: String) extends
PersistentActor {
// … persist events, handle recovery...
}
// test:
val act = sys.actorOf(Props[MyPersistentActor](“id-1212"))
act ! “persist-me-1”
act ! “persist-me-2” // persist(){} those
val act2 = sys.actorOf(Props[MyPersistentActor](“id-1212”))
// recovery kicks in, because they get the same persistenceId
act ! “what’s the last persist-me-### you got?”
expectMsg(“persist-me-2”) // because recovery
I hope this helps, happy hakking!
--
Konrad 'ktoso' Malawski
hAkker @ typesafe
http://akka.io
--
>>>>>>>>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
