When JObject is used for messaging then Akka fails to route such messages due to serialization problem.
In my particular case I have a strong typed message class with IDictionary<string, object> property and Akka.Serialization.Hyperion configured as default serializer. At some moment this dictionary may contain JObject. Such messages destroy actor life-cycle due to serialization problem.
System.NullReferenceException: Object reference not set to an instance of an object.
at Hyperion.SerializerFactories.DictionarySerializerFactory.<>c__DisplayClass3_0.<BuildSerializer>b__1(Stream stream, Object obj, SerializerSession session)
at Akka.Serialization.HyperionSerializer.ToBinary(Object obj)
at JObjectSerializationTest.UnitTest.<>c__DisplayClass1_0.<ShouldBeSerializedByHyperion>b__0(Serializer serializer, Object entity)
When JObject is used for messaging then Akka fails to route such messages due to serialization problem.
In my particular case I have a strong typed message class with
IDictionary<string, object>
property andAkka.Serialization.Hyperion
configured as default serializer. At some moment this dictionary may contain JObject. Such messages destroy actor life-cycle due to serialization problem.I made a test project to illustrate such behavior JObjectSerializationTest.zip
Used packages versions