0

For an unknown reason, MassTransit keeps moving messages of a specific type to the error queue. I believe that a deserialization error is causing this.

What's the best way to debug deserialization errors?

Community
  • 1
  • 1
Jim G.
  • 15,141
  • 22
  • 103
  • 166

1 Answers1

0

The easiest way to figure out what's going on is enable one of the logging providers and look at the logs for a given consumer that's kicking stuff over. You might need to configure specific loggers, anything under MassTransit would be helpful.

In addition, I believe Chris added the some information to the envelop in a recent version of MT. You might be able to identify the error just by looking at the JSON or XML payload envelop in the message queue.

Travis
  • 10,444
  • 2
  • 28
  • 48