-
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
NullReferenceException in Akka.Persistence.Serialization.MessageSerializer.PersistentPayloadToProto #1235
Comments
cc @Horusiath @rogeralsing any ideas why this was dependent on |
…here to the practice of including an addres with the serialized binary.
Fixes the NullReferenceException in #1235
As I remember, after a short discussion with Typesafe team they pointed us out, that things like actor refs and paths that are stored, may be recovered from persistence backend on the different machine, that they were saved on, so their base paths may be changed. |
Is this still an issue? or did trbngr@3df119f fix it? |
Closing that one. No updates in the last 9 months. |
I'm trying to run tests after Akka.Persistence.Cassandra was upgraded to use Akka 1.0.4 and I'm consistently getting a NRE like this:
Looks like it's coming from this line here:
https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka.Persistence/Serialization/MessageSerializer.cs#L140
When
TransportInformation
is null. I'm guessing fb03e9d may have introduced the issue. Not sure if fixing this is as simple as just adding a null check onTransportInformation
before calling theAddress
property or if that property shouldn't be null in this case indicating some other bug.The text was updated successfully, but these errors were encountered: