If you have to set the max pool to 1000, you know you're doing something
wrong :)
It appears from the code snippet that you only want to have a single
connection object, which is open as long as the calls coming in are using
the same connection string. If so, wouldn't this object need to be Shared
Just to straighten some...
I always perform my close and
dispose within the finally section of a try-catch-finally block. As a
last item, I also mark the objects for deletion by specifically setting
the objects to null/nothing.
- It is not needed to call both Dispose and Close in the same line
Hi Stefan!
I have the same problems, I'ge gone through my code several times and i'm
sure I close everything!
BUT, when i xcopy the project to my Win2000 server it all works fine!
What is yor config?
I use WinXP / IIS5.1 / VS.net 2003
/Rob
-Original Message-
From: Stefan Heunis [mailto:
I have seen this problem before. Heath is exactly right, the connection is not being
closed and returned to the pool. The next problem is going to be that under a heavy
load, you may still have a failure. To resolve this, you will want to call .Dispose()
on all database objects and objects th
just check if ur using any static method in ur
data access block.
r.
-Original Message-
From: Stefan Heunis [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 2:33 PM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] The timeout period elapsed prior to obtaining
a connection from
In the Ntypes you can see some advanced C# programming applied in the source
code that may interest you:
- the ?null object? refactoring pattern applied (this is what Ntypes does on
.NET built-in types)
http://www.refactoring.com/catalog/introduceNullObject.html
from "Refactoring: Improving
I too feel the same. It's better to add finally{ connection.close()} in all
the methods where ever this connection method is getting called.
Raga Deepika Addagalla
SEEC Technologies Asia Pvt. Ltd.
Phone: +91-40-23742506/23742507 X.41
-Original Message-
From: Heath Ryan [mailto:[EMAIL P
Hi Stefan,
Looks like your are not closing connections that were succesfully
opened, but then again I do not have your full source code :)
HTH,
// Ryan
-Original Message-
From: Stefan Heunis
To: [EMAIL PROTECTED]
Sent: 9/26/2003 11:03 AM
Subject: [ADVANCED-DOTNET] The timeout period
Hi,
I get the following error in a volume creation program, when the program try
to open the SQL Connection.
The program executes the same code successfully a number of times before it
stops.
I have changed the Max Pool Size to 1000 but it does not make a difference.
Method : GetValidSQLConnecti
Try Decoder.GetChars then StringBuilder.Append, ToString. Make sure you
remove any BOM if present.
-Jeff WS
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Fernando Tubio
Sent: Thursday, September 25, 2003 2:59 PM
To: [EMAIL PR
10 matches
Mail list logo