Re: Connection pooling and changed password issue

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 03/15/05 

Date: Mon, 14 Mar 2005 17:41:04 -0800

Nope. There is no "clear the pool" or "drop the pool" until ADO.NET 2.0. 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Siobhan" <Siobhan@discussions.microsoft.com> wrote in message 
news:64F49230-1E5C-405D-BBEB-0A23AF1D9578@microsoft.com...
> Hi - so a previously made connection with the old credentials will still 
> be
> retrieved from the pool until it times out?  And there is no way to get 
> rid
> of this pooled connection other than its timeout?
>
> It is an ASP.Net application and credential do change as each user has 
> their
> own database login (the system is intranet).  Each user requires their own
> login for purposes of audit and we also assign users to roles to restrict
> access to data and certain functionality depending on their role.
> Thanks
> Siobhan
> "William (Bill) Vaughn" wrote:
>
>> If the connection string changes, a new pool is created--it's that simple
>> (almost). A pool lives until it's empty or the application ends. Unused
>> connections in a pool time out after 4-8 minutes. If you're changing
>> credentials, you should get a connection that matches your connection 
>> string
>> (using the supplied credentials).
>> If this is a Windows forms application you don't typically gain much from 
>> a
>> connection pool as there are so few connections. If building an ASP
>> application you don't typically collect user credentials--you usually use
>> the ASPNET account.
>> hth
>>
>>
>> -- 
>> ____________________________________
>> William (Bill) Vaughn
>> Author, Mentor, Consultant
>> Microsoft MVP
>> 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.
>> __________________________________
>>
>> "Siobhan" <Siobhan@discussions.microsoft.com> wrote in message
>> news:385C24B3-C605-485B-8EFC-2CB6F1169A42@microsoft.com...
>> > Hi
>> > I have a problem I suspect is to do with connection pooling.  If I 
>> > connect
>> > as username/password, and the dispose of the connection am I correct in
>> > thinking the next time I connect to the same datasource with
>> > username/password then the connection pool will be used and the same
>> > connection can be used at less overhead.  This is fine, however if I
>> > change
>> > the password to password2 I can connect as username/password and
>> > username/password2.  I can only assume this is because the pool is 
>> > still
>> > holding a valid connection as username/password.
>> >
>> > Where I am confused is that on occasion I have logged in as
>> > username/password, chnaged the password and immediately tried to login
>> > again
>> > as username/password and it immediately fails.  If I then login as
>> > username/password2 I can connect and then if I connect as
>> > username/password
>> > it will connect again after previously failing.  Eventually the old
>> > password
>> > will fail if I leave it long enough, again I assume this is because the
>> > connection has been idle for the specified time and is cleared out of 
>> > the
>> > pool.
>> >
>> > As I understand there is no way at the minute to clear one particular
>> > connection out of the pool so is there any way round this issue?
>> > Thanks in advance
>> > Siobhan
>>
>>
>>

Relevant Pages

  • Re: Close and Dispose argument
    ... > fact that even Microsoft is not clear on the issue. ... > connections from the pool is still a debate. ... > method removes the conneciton from the connection pool". ... > Your issue was forwarded to us here at Microsoft Courseware Support. ...
    (microsoft.public.dotnet.framework.adonet)
  • Close and Dispose argument
    ... here is an email conversation between me and Microsoft ... connections from the pool is still a debate. ... Programming with Microsoft ADO.NET" module 2, p 18: "Calling the Dispose ... method removes the conneciton from the connection pool". ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: MinPoolSize behaviour
    ... Min Pool Size, The first time you open a connection we will open the 1 ... > Is the pool created forever? ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Q:Multithreaded ADO.Net Connections Are Non Pooled?
    ... different you get a new pool. ... > the process/app domain differences, does running on a thread created by ... If you're using SSPI, each connection must be ... >> connect to the SQL Server machine, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Connection pooling and changed password issue
    ... If the connection string changes, a new pool is created--it's that simple ... A pool lives until it's empty or the application ends. ... If I connect> as username/password, and the dispose of the connection am I correct in> thinking the next time I connect to the same datasource with> username/password then the connection pool will be used and the same> connection can be used at less overhead. ...
    (microsoft.public.dotnet.framework.adonet)
Loading