or is this handled by the base class "Testkit"?
but is it normal that after test completes there are so much debug log entries like
DeadLetter from [akka://test/user] to [akka://test/user]: <<DeathWatchNotification>: [akka://test/user/TestProbe_DetailPageVersion_9c57b66d-5cc9-4b73-8ad4-d4bdef0ad324], ExistenceConfirmed=True, AddressTerminated=False>
do I have to collect these DeathWatchNotifications by myself?
or can I suppress them?
Thus the deadletter logs
nothing to worry about.
So not at this time
much nicer commandline experience for Windows
I just replace the entire HOCON section full stop
Question on Cluster Sharding: Can you have more than one instance of a given type of entity on a single Node? The only statement I could find of this issue was "One entity instance may live only at one node at the time" in the documentation, but I'm not really sure what that is supposed to mean.
@cfjames yes you can. This statement means, that if you have for example actor representing User with id=1, you may be sure that as long as cluster is not partitioned, no more than one actor representing that user will be present at the same time, keeping your user state consistent
When Lighthouse is running and a node where a Sharding Region starts, I see the following message in the Lighthouse logging: "Messge Register from akka.tcp://clustername@ip:port/user/sharding/typename to akka://clustername/user/sharding/typenameCoordinator/singleton/coordinator was not delivered"
ok. i seem to forget something. i have a topshelf service running an actorsystem and i added all the akka.remote stuff and put the config in the app.config and the logs show me the actorsystem gets started with that config. but it doesn't open up a port to listen to when i start the service in the debugger. do i still need something else?
@schepersk you probably need to restrict your cluster sharding to nodes not being lighthouse. One of the available sharding settings is the role, which tells what role does a cluster node need to have in order to support cluster sharding - without it, shard region will assume, that all nodes are capable of sharding (while lighthouse is not)
@andreabalducci no, it's not possible, persistence id describes boundaries of write operations for persistence
@Horusiath So, does this also mean that you can restrict the type of a shard to a node role? Lets say you have a shard region for AR1 running on role ABC and you want to start a shard for AR2 on a completely different node with role XYZ..
you can have role like 'sharding-enabled' and simply refer to it from sharding settings
okay, but what about service1 in the cluster with 2 instances (nodes), hosting shards for its entities. Then service2 is ready to join the cluster with some instances (nodes). Each of these services have their own cluster sharding configuration. So my guess is that it should be possible to keep the entities from migrating to nodes where they don't "belong" ?
@Horusiath I'm seeing these log entries.. Any thoughts?
Akka.Actor.LocalActorRef: Message WriteMessagesSuccessful from akka://bm2cluster/system/akka.persistence.journal.sql-server to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 8 dead letters encountered.
Akka.Actor.LocalActorRef: Message WriteMessageSuccess from akka://bm2cluster/temp/mb to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 9 dead letters encountered.
Akka.Actor.LocalActorRef: Message WriteMessagesSuccessful from akka://bm2cluster/system/akka.persistence.journal.sql-server to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 8 dead letters encountered.
Akka.Actor.LocalActorRef: Message WriteMessageSuccess from akka://bm2cluster/temp/mb to akka://bm2cluster/user/sharding/LoonbonVerwerking/2/7afca3c0-e26c-4a97-89a5-4dd9883533b6 was not delivered. 9 dead letters encountered.
Maybe because they already got passivated before persistence could provide feedback?
SQL Server persistence plugin works in 1.0.7 if I build it from sources but when I use a version from NuGet I get TypeLoadException
{"Method 'DeleteBatchMessages' in type 'Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder' from assembly 'Akka.Persistence.SqlServer, Version=1.0.6.3, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder"}
{"Method 'DeleteBatchMessages' in type 'Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder' from assembly 'Akka.Persistence.SqlServer, Version=1.0.6.3, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"Akka.Persistence.SqlServer.Journal.SqlServerJournalQueryBuilder"}
I see that none of NuGet packages for the actual persistence plugins has been updated to 1.0.7 on NuGEt.
so i have a question. i have an actor that gets a message from a remote client. in this message is information about a class this actor should retrieve from the container and a method and a bunch of params that the actor should call as well as the return type. so i have this actor that retrieves the object form the container, checks if there's a method on that class that fits the description of the message and then tries to call it with
Invoke(). so far so good. it is all working so far. i put this Invoke() call inside a try catch block because i basically want to tell the sender if something happened to while calling the method and basically return the thrown exception as a message back to sender. but when the invoked method itself throws a TargetInvocationException because of reasons it seems the actor just dies. and i get some disassociation messages in the log and stuff like that. it's like the try catch block inside the receive method is just not working. any hints?