-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Akka: serialize-messages barfs on built-in Akka.Cluster / Akka.Remote types #3724
Comments
You know what... The issue here might be that some of the internal messages we pass around, internally, inside the |
Aaronontheweb
added a commit
to Aaronontheweb/akka.net
that referenced
this issue
Feb 26, 2019
Aaronontheweb
added a commit
to Aaronontheweb/akka.net
that referenced
this issue
Feb 26, 2019
Also, disabled serialization verification for internal `PublishChanges`
madmonkey
pushed a commit
to madmonkey/akka.net
that referenced
this issue
Jul 12, 2019
) close akkadotnet#3724 - provided JSON constructor for Member disabled serialization verification for internal `PublishChanges`
Aaronontheweb
added a commit
to Aaronontheweb/akka.net
that referenced
this issue
Jul 30, 2019
) close akkadotnet#3724 - provided JSON constructor for Member disabled serialization verification for internal `PublishChanges`
Just thought I'd contribute another serialization bug using
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: Akka.NET v1.3.11
Issue:
When
akka.actor.serialize-messages = on
, built-in Akka.Cluster and (possibly) Akka.Remote get serialized with JSON.NET (the defaultobject
serializer) instead of their specific serializer registrations, and thus this exception gets thrown:Reproduction from @Dan-Albrecht: https://github.com/Dan-Albrecht/AkkaRepro
Suspect that the issue is that the underlying
serialize-messages
code isn't correctly looking up the customer serializer correctly.The text was updated successfully, but these errors were encountered: