Hello, to address the startup warning regarding no explicit serializer set, we decided to set the default serializer to JSON. This lead to a deserialization failure. We reverted to XML.
The message that failed has a property of type System.Exception. The message was sent with a custom subclass. This resulted in the error “An error occurred while attempting to extract logical messages from incoming physical message”. The specific message is “Message: Member ‘HelpURL’ was not found.”
Some Googling suggests the problem is within the NewtonSoft JSON deserializer. While I think this is probably a bad design, to declare a base class as a type, the fact is it works as expected (yields a deserialized Exception, not the actual subclass type) with XML as the serializer.
As said, we reverted to XML. We expect to use JSON as a supplemental deserializer for native SQS support only. We don’t have a blocking condition here, but just provide this description of our experience should you wish to pursue a bug fix.