From: Andrew G. <ag...@jc...> - 2003-03-14 17:37:38
|
Thanks. Pooling=3DFalse;=20 In the connectionstring did the trick. :) Andrew. -----Original Message----- From: Carlos Guzman Alvarez [mailto:car...@te...]=20 Sent: Friday, March 14, 2003 11:10 To: Andrew Goodall Cc: fir...@li... Subject: Re: [Firebird-net-provider] interbase user physical connection not disconnecting. Hello: > Thank you all for the previous help you have provided - you have been a= =20 > real help getting me up and going. I can now select, update, insert, etc= =20 > as desired from my asp.net webform to my interbase db. >=20=20 > My question is concerning the physical disconnecting from the database.= =20 > In my code I make sure I dispose the Transaction, Command and Close the= =20 > Connection. > Everything appears to be fine, I receive no exceptions on the dotnet=20 > side. But when I go to Interbase I view the connected users it still=20 > shows the user connected. > The user will only disconnect after I recycle IIS 5.0. >=20=20 > Any ideas why the user will not disconnect from the database? > Is this related to connection pooling and/or garbage collection in dotnet? >=20=20 > Below are snipets of VB.Net code examples I use to connect and disconnect. This seems to be a problem with Connection Pooling, you can set in=20 connection string the Connection Pooling off, default is on, or change=20 the Connection Lifetime, default is 0. --=20 Best regards Carlos Guzm=E1n =C1lvarez Vigo-Spain "No tengo dones especiales.S=F3lo soy apasionadamente curioso" Albert Einstein, cient=EDfico. |