[akka-user] Timing of eventsByTag() and persist()

We are seeing some baffling behaviour in a unit test (using akka-persistence-inmemory). The test starts actor A and actor B (which starts a stream using eventsByTag in its RecoveryCompleted handler). The test then sends commands to actor A, which results in appropriately tagged events being

[akka-user] Using "Distributed Data" for caching Tokens. Delete by value with LMWMap possible?

Hello, I'm using Distributed Data for caching Authorization-Tokens: private final Key dataKey = LWWMapKey.create("cache"); // token -> CustomerId When the password of a customer is changed, all Tokens for this Customer be removed. How is this possible, or is it even possible? Thanks

Re: [akka-user] `ActorSystem.whenTerminated` hangs indefinitely if called from an `registerOnTermination` callback

Hi Chris, On Tue, Nov 15, 2016 at 1:46 PM, oxbow_lakes wrote: > The following code: > > Welcome to Scala 2.12.0 (Java HotSpot(TM) 64-Bit Server VM, Java > 1.8.0_112). > Type in expressions for evaluation. Or try :help. > > > scala> import akka.actor._; import

[akka-user] `ActorSystem.whenTerminated` hangs indefinitely if called from an `registerOnTermination` callback

The following code: Welcome to Scala 2.12.0 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_112). Type in expressions for evaluation. Or try :help. scala> import akka.actor._; import scala.concurrent._; import duration._ import akka.actor._ import scala.concurrent._ import duration._ scala>

[akka-user] Re: Akka cluster sharding messages default serialization

I'm going to answer my own question here. It turns out that akka-cluster-sharding registers its own serializer which is based on protobuf. It's a bit hard to find because it's all private but here is it on Github:

[akka-user] Akka cluster sharding messages default serialization

Hello, we do event sourcing with akka-persistence and akka-cluster-sharding. Apart from our own messages/events akka-cluster also writes a few messages regarding shard allocation to our event log. We have configured a custom serializer for our own events which transforms them to JSON but