admin管理员组

文章数量:1180493

I'm using MT version 8.3.0 with rabbitmq. In testing, I got this rare error message on the error queue with the below headers which I haven't been able to reproduce on demand.

This happened on a saga scheduled message when database was under heavy load.

TypeMapper property is an obsolete property, all it does is throwing the NotSupportedException.

My guess is that some process in MT tried to serialize an exception which contained the NpgsqlConnection object, perhaps before moving the message to error queue. The message and stackTrace are not related to the real exception the application threw.

How can I remove the NpgsqlConnection from the exception or stop serializing it so that I can see the real excpetion?

本文标签: netMasstransit exception serialization cause a different exception to be thrownStack Overflow