We've been having problems lately with user sessions staying "connected" for days, and we have to go in and manually kill them. The problems dont seem to be specific sql statements. At least we cant find a pattern when we look at these never ending sessions. What will often happen will be complaints about the db "running slow" and we check the sessions, locate sessions that have been connected for hours/days, kill those sessions and performance goes back to normal.
About a year ago we had to switch from dedicated to shared server connections and that seems to be when the problem started.
I dont find any errors or anything to point me in the right direction. Is there any parameter that can be set so that these never ending sessions can be automatically killed after a timeout or something??
any suggestions would be appreciated
About a year ago we had to switch from dedicated to shared server connections and that seems to be when the problem started.
I dont find any errors or anything to point me in the right direction. Is there any parameter that can be set so that these never ending sessions can be automatically killed after a timeout or something??
any suggestions would be appreciated