nullreferenceexception - NServiceBus ServiceInsight All Messages Get Routed To ServiceBus.Management.Errors -
i have service configured handle command object. in handle method throwing exception in specific business cases. when occurs send error error queue , think particular management service processing error queue. understanding particular management service monitor error queue , process messages, say, mine metadata , persist ravendb. lastly, should forward message error.log queue. regrettably, every message seems routed service.management.errors queue. presumably, because particular management service handler failing.
if extension headers of messages in service.management.errors queue, see following information:
<headerinfo> <key>nservicebus.exceptioninfo.exceptiontype</key> <value>system.nullreferenceexception</value> </headerinfo> <headerinfo> <key>nservicebus.exceptioninfo.message</key> <value>object reference not set instance of object.</value> </headerinfo> <headerinfo> <key>nservicebus.exceptioninfo.source</key> <value>nservicebus.core</value> </headerinfo> <headerinfo> <key>nservicebus.exceptioninfo.stacktrace</key> <value>system.nullreferenceexception: object reference not set instance of object. @ nservicebus.unicast.transport.transportreceiver.processmessage (transportmessage message) in c:\teamcity\buildagent\work\d4de8921a0aabf04\src\nservicebus.core\unicast\transport\transportreceiver.cs:line 357 at nservicebus.unicast.transport.transportreceiver.tryprocess(transportmessage message) in c:\teamcity\buildagent\work\d4de8921a0aabf04\src\nservicebus.core\unicast\transport\transportreceiver.cs:line 235 @ nservicebus.transports.msmq.msmqdequeuestrategy.action() in c:\teamcity\buildagent\work\d4de8921a0aabf04\src\nservicebus.core\transports\msmq\msmqdequeuestrategy.cs:line 170
since serviceinsight particular management service presumably supposed generic in nature, assume not need know actual types of messages. meaning, don't have throw message dll's directory of service (correct?). implying mines of it's data persist ravendb reading extension headers.
so ground work in place. can please validate or invalidate understanding of how serviceinsight works , configured. secondly, error looks error in nservicebus.core. supposed add dll's or something. of there candidate causing issue overlooking.
we having similar problem, , although our problem pretty specific us, i'll share in case.
most of our services use nservicebus 4.0.3 xml serialization, have 1 older service using nsb 3.3.1 , binary serialization. service logging audit queue, , when particular management service tried read messages, fail. i'm not sure source of error was, due nsb re-throwing exception , losing original stack trace. suspect trying read header isn't there. may due using binary serialization.
our solution turn off auditing 1 older service.
Comments
Post a Comment