The process was terminated due to an unhandled exception

2

Hi Raj

NServiceBus is now out of general support but looking at the code here it seems that the process is killed because in V5 only the QueueNotFoundException was handled properly. In case of any other exception, it is propagated to the calling code (which in this case is the Thread Pool) and the process is killed.

I suspect there is some connectivity issue with the SQL Server database here but in order to diagnose it you have two options:

  • connect the debugger and put a breakpoint in SendSubscribeMessageWithRetries
  • modify the code in SendSubscribeMessageWithRetries to catch all types of exceptions rather than only QueueNotFound and at least log the exception details. Then build and run your custom version of NServiceBus. Note: after diagnosing the problem you can revert back to the official package.

Szymon