Causing query Timeout at the StoredProc level

I've been looking at this problem for a while now and I want to get
some other insights.
I have some mysterious "hanging SPIDS" happening on my system from a
web based application if the users press the back button or refresh.
As if the connection pool does not clear the connection properly. I'm
looking for a procedure level solution to this, so options in
sp_configure would be a no go. I've already looked at SET LOCK_TIMEOUT
and QUERY_WAIT options and they don't seem to do what I want. Aside
from going back to my developers I'm stumped.Going back to the developers is where you need to go, otherwise anything you
do will most likely be a hack. Connection pooling is pretty rock solid and
it is most likely issues with how they are coding the app not anything with
the connections or SQL Server.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Pawn" <TheRealPawn@.gmail.com> wrote in message
news:413eb287-0b95-43c0-8898-8fc90057dedb@.i7g2000prf.googlegroups.com...
> I've been looking at this problem for a while now and I want to get
> some other insights.
> I have some mysterious "hanging SPIDS" happening on my system from a
> web based application if the users press the back button or refresh.
> As if the connection pool does not clear the connection properly. I'm
> looking for a procedure level solution to this, so options in
> sp_configure would be a no go. I've already looked at SET LOCK_TIMEOUT
> and QUERY_WAIT options and they don't seem to do what I want. Aside
> from going back to my developers I'm stumped.