William
Wed Jan 04 13:57:33 CST 2006
Ah, what you're seeing is the Connection Pool holding the connection open
long after you close it. If you stop the application, the pool is torn down
and all of these "agents" (sleeping processes) are ended.
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Abelardo Vacca" <AbelardoVacca@discussions.microsoft.com> wrote in message
news:0E84AFFE-9825-49C8-85B0-BBDE55336073@microsoft.com...
> Thank you Bill.
>
> Actually, the application is ALWAYS leaving an "agent" open per user
> session
> (only ONE per session) .... even after all ADO.NET connections are closed
> !!!! (or at least I think they are) ... even after the session is closed
> ...
> these "agents" remain for a few minutes before they time out. - The good
> thing is all requests are using the same "connection" (agent), so I
> suppose
> these are not connections left open -
>
> Is this he case you refer to as normal?
>
> Thanks again for the help.
>
>
> --
> Abelardo Vacca
>
>
> "William (Bill) Vaughn" wrote:
>
>> 100% normal. This is your connection's "agent" that does all the work
>> requested by the connection. It's closed down when the connection closes.
>>
>> --
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> INETA Speaker
>> www.betav.com/blog/billva
>> www.betav.com
>> Please reply only to the newsgroup so that others can benefit.
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> __________________________________
>>
>> "Abelardo Vacca" <AbelardoVacca@discussions.microsoft.com> wrote in
>> message
>> news:9A5DB456-B950-4C14-98CE-6B52B65C1741@microsoft.com...
>> > Hello,
>> >
>> > I have a web application accessing SQL Server 2K through ADO.NET
>> >
>> > The application is working fine, but while monitoring the processes in
>> > SQL
>> > Server Enterprise Manager, I noticed each user connecting to the
>> > application
>> > creating a NEW process in "awaiting command" state.
>> >
>> > I would like to know if this is normal, do "awating command" processes
>> > represent connections left in an open state?
>> >
>> > Thank you
>>
>>
>>