Database Connection not getting reset after a application timesout
We have an application that points to our SQLServer 2016 database. Changes were made to the front-end application and since then we are seeing intermittent timeouts.
The application seems to be timing out since the SP called does not complete on time due to CXCONSUMER waittype. While we are addressing the parallelism issue as indicated by CXCONSUMER we dont know why the database connection is not getting reset. Normally, the connection timeout would show up in the Attention alert of Profiler but it is not showing up either.
Another issue is that killing the database connection itself does not address the problem. The SP needs to be recompiled before a new connection can be successfully established.
Has anyone come across similar issue before?
I am not sure that I follow. Are you saying that you get "Timeout Expired", but there is no Attention event seen in SQL Server?
Do you actually need the timeout? Or could you permit the query to run for a longer time?
Sign in to comment
Hi, Just following up. Is there any update on this case?