New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serialize-messages =on doesn't work with DistributedPubSub #4120
Comments
Can confirm that the cluster system does not correctly form and end up getting the following at the publisher. If I turn serialization back off, everything works as expected. [INFO][22/12/2019 12:44:39 AM][Thread 0005][Cluster (akka://PubSubSystem)] Cluster Node [akka.tcp://PubSubSystem@192.168.0.29:123] - Received InitJoin message from [[akka.tcp://PubSubSystem@0.0.0.0:3212/system/cluster/core/daemon/joinSeedNodeProcess-1#1491684597]], but this node is not initialized yet |
@MaximG1234 thanks for reporting this - thought we had fixed it already in #3725 but that must not be the case. |
#3791 might contain a fix |
So this isn't an issue with Akka.Remote or Akka.Cluster - it appears to be an issue with Akka.Tools.DistributedPubSub, based on your reproduction sample. I'm going to push a reproduction spec here shortly. |
…ion breaks clustering
Taking this off of the 1.4.0 milestone - it's a minor issue and ultimately a problem because Newtonsoft.Json can't handle Systems.Collections.Immutable. Not getting a clear beat on which specific messages are causing the issue in #4721 but I'll leave this up for grabs. |
Akka.NET 1.4.0-beta3
It appears that enabling 'serialize-messages = on' while using clustering breaks the actor system with the following error.
Looks like clustering has some difficulty correctly serializing its messages when turned on.
Here is a project which reproduces the error https://www.dropbox.com/s/o9al6adwl609p7o/AkkaTest.zip?dl=0
The text was updated successfully, but these errors were encountered: