I have windows service where i using NServiceBus. Randomicaly NServiceBus stop dequeuing message from queues and for restart dequeing i need to restart the service.
On NLog config i have setup the info log level and i can’t find significatice log.
I use:
NServiceBus version: 7.5.0
NServiceBus.Persistence.Sql 6.2.0
NServiceBus.Transport.SqlServer 6.3.1
I can not activate trace log for transport because the daily log file was etremely big
The log levels is set to default but in the file there aren’t anything, if you have suggest for log something is perfect. The problem happen in the one application
I’m experiencing the same behavior — the endpoint silently stops dequeuing messages with no errors or warnings in the logs. The only resolution is restarting the service, after which processing resumes normally. In one instance, over a million messages had accumulated in the queue and it took three restarts of the host to fully clear the backlog.
Unfortunately, I wasn’t able to run sp_who or sp_who2 at the time of the incident, but I’ll make sure to capture that information the next time it occurs.
Is there any additional logging or diagnostics that can be enabled on the transport level to help identify the root cause? Any configuration that might surface what’s happening when the dequeuing stalls would be greatly appreciated.