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
Hi,
Does this only happen in the one application or does it happen in more than one?
Based on the transport and persistence, there might be some clues in the log files related to SqlConnection failures.
If the log file is set to default log levels, are there any WARNs or FAILs in the log file? Anything to give us a clue to get started.
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
Do the other applications connect to the same instance of SQL? Can you look at SQL and see what applications are executing what scripts when it stops?
sp_who and sp_who2 would be helpful here.
I checked the other instances the scripts they run and none of those impact the tables of the service that crashes
Can you look at sp_who and sp_who2 when the application is stopped to see the server is doing?