hi i'm having this error on my application"cannot allocate more connection.connect pool is at maximum increase max pool size" the proble is when i do testing this error does not apply it only Appears when the application is been used by many people
How can I resolve this?
Thanks
What does this error message imply?
View 3 Replies View RelatedHello.
I have a db dal containing the following code:
SqlCommand cmd = new SqlCommand();
cmd.Connection = dbc;
cmd.CommandType = CommandType.StoredProcedure;
cmd.CommandText = "SOME STORED PROCEDURE";
.
.
.
declare some SqlParameters
.
.
.
dbc.Open();
cmd.ExecuteNonQuery();
dbc.Close();
This code, when concurrently running via several threads, yields the following exception:
"The connection was not closed. The connection's current state is open."
My questions are:
1. Why don't .Net allocate another connection from the pool (I try to only concurrently run 2 threads while there are 25 connections in the connection pool) ?
2. How can one explicitly allocate a connection?
3. How do you suggest to solve this problem without a mutex/monitor etc' on the 3 bold lines above and without BeginExequteNonQuery()?
Thank you !
Hi to all,
I am using a connection string like
data source=RemoteHostName;initial catalog=myDb;password=sa;user id=sa;
Max pool size = 200;
And now strange thing is happening ,, I am receiving error :
Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were in
use and max pool size was reached
The SqlServer Activity Manager is telling that only 100 connections are pooled, and I guess that the Max pool size is 100, It is not being changed by my Connection string. As I am trying to change the default 100 pool size value to 200.
Huh , So stucked up , how to increase the Max pool size.. Is there any way .
I am getting worrried.
Any help ??
Thx and Regards
Hello Experts,I make a connection with .Net Sqlclient Data Provider tomy server and I adjust the min pool size = 0, but when Icheck the sysprocesses I see that 2 connections have beenmade. Why is that? am I missing something here?Conn. string"server=MYSERVER;user id=sa;database=MYDB;min poolsize=0;max pool size=10;packet size=3072;ApplicationName=MYAPP"Thanks in advanceMichas KonstantinosSQL Sewrver Developer, DBA*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
View 1 Replies View RelatedI have a site which provides online studying for students in a graduate program. Apparently their final was today because lastnight everybody was on. I know, however, that this is a small class, so no more than about 80 people could be on the site at one time. I still got SQL errors (emailed to me from Application_Error). I read on MSDN that by default connection pooling should be in place, with a pool size of 100... that would mean I wouldn't have this problem if only 80 students were on the site.
Why is this happening?
Below is my connection string from web.config.
<add key="connStr" value="Server=xxxxxx;Database=xxxx;UID=xxx;PWD=xxx;"></add>Error:
System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
msdn link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconnectionpoolingforsqlservernetdataprovider.asp
Dear All,
how can i change the default pool size???
Vinod
Even you learn 1%, Learn it with 100% confidence.
When using connection string connect to sql server, there is a item max pool size.
The default is 100.
I set it to 500, but still get max pool size is reached and timeout error.
I checked my code and do open and close each connection each time using connection, so should have no memory leak.
What is the maximun value for max pool size? how to calc this size based on the memory used by SQL Server?
How to find max pool size in sql server 2012?
View 2 Replies View RelatedI am working on a large application built on the 1.1 framework in VS2003 (SQL Server 2000 DB) and keep getting this error:
'Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached'.
I can run the app in Debug 10 consecutive times, doing the exact same thing every time, and the error will occur at 10 different points, and 10 different calls to the data-access layer.
There is a data-access layer that is responsible for executing sql statements and stored procs. Every function in the data-access layer handles connections in the following way:
Try ' setup data adapter da.Fill(ds, "ResultSet") Return dsCatch ex As Exception ' send the exception back to the client Throw exFinally ' release objects da.Dispose() conn.Close() : conn.Dispose()End Try
I have read numerous posts about making sure not to leak connections. I have watched the connections within the SQL Activity Monitor and, at the most, there are 5 connections open at any given time. I use the default timeout and pool size values (30 sec. and 100 connections) in my connection strings. I am 99% positive that I am not leaking connections. Are there any other explanations for why this is happening?
I build an asp.net 2.0 (VS 2005) web application and put it on the server. The installed SQL server is SQL server 2003. I get this error message when i keep the application running for 10 or 15 mins. "Timeout expired. The timeout period elapsed prior obtaining a connection from the pool. This may have occure because all pooled connections were in use and max pool size was reached."
I made the server timeout unlimited but the error keeps coming up after some time of openning the application. The application session time out redirects the user to the login page and doesn't throw an error like the one i mentioned above.
Any idea. Thanks in advance.
hello to all
my problem is
when in database it reaches nearly 100 active connections (i check it from detach database) , my application does not allow me to open new browser page and show me error like:
time out expire. the max connection pool is reached.
please help.
how can i change pool buffer of all connections?
I receive this error for each connection:
System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Hi guys!
I have a dev server that has about 15-25 connections which is fine.
**
Looking at performance counters: _global_
under SqlClient: Current # connection pools
under SqlClient: Current # pooled connections
under SqlClient: Current # pooled and nonpooled connections
**
BUT when I look at staging and production I have only 4 or so...
WHAT'S GOING ON?!?! The querystring doesn't specify the max pool
size, pooling, nor timeout values. So I'm guessing it uses the
defaults. ( I also tried putting in max pool size, but it didn't
change anything! )
Does anyone know how I can increase the value? It is impacting the performance of the site considerably. Thank you!
From what I understand, some database drivers provide automatic database pooling, in the sense that when an application closes a connection, it is not dropped until after a certain timeout. If the same, or another application, request a connection then the "pooled" one is returned.
What's the situation with C#, .NET Compact Edition and SQLce? Is it a performance hit to open and close a connection, or is some kind of automatic pooling in effect?
Thanks.
Martin
How do i check the size of the datacache allocated from the buffer pool by sql server?
DMV or anything to show me the pool allocation sizes for the various pools in sql server i think i may be able to work from there.
Hi All,I'm having a bit of a problem with a c# program which creates and index file/table. The number of records I need to process is around 3500, the main loop. Each of thoes records I need to look at a 2 text fields and create an entry in an index table for each valid word found in thoes fields. I call a stored proc to save the key word. So this stored proc get called numerous time per record.What seems to be happening is proceese about 400 main rcords the errors out with the following error message: {"Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached." }Has anyone had a similar problem? if so any suggestions on how to fix, I've been looking at this problem and recoding for the last 4 days! I need some help! Using SQL Server 2000 & .net v1.1Thanks in advance Davej
View 1 Replies View RelatedHi All,
Where Connection pool reside, is in client side(in .net framwork) memory or at server(in sql server) momory or at both side it maintains pool information?
Best RegardsImran Zubair
I'm opening a large number of connections to a SQL server 2005 database using a SQL object based on the System.Data.SqlClient library. When I log out of the application, I call the ClearSQLConnectionPool method of the SQL object and this should clear the pool of these connections. This has worked in the past, but lately I have noticed some odd and very annoying behaviour.Very often I log out of the application and few, if any of the connections disappear. Just this morning I opened the application, logged out and all but one of the connections disappeared. Then I opened it again, logged out and none of the connections had gone. If I open the application again all of the past connections are still there plus the new ones.I know it works, its just very inconsistent. The problem may be with IIS, SQL or with library; I just can't tell which.Any ideas?Many thanks
View 1 Replies View RelatedDear GroupSorry for posting this here. I'm desperate for a solution to thisproblem and thought some of you might have come across it with .NETand SQL Server.Let's assume I've the following code:Private Sub Button4_Click(ByVal sender As System.Object, ByVal e AsSystem.EventArgs) Handles Button4.ClickDim sqlConnection As New System.Data.SqlClient.SqlConnectionsqlConnection.ConnectionString = "workstation id=THEINTREPIDFOX;packetsize=4096;user id=sa;data source=""(local)"";p" & _"ersist security info=False;initial catalog=TestDB"sqlConnection.Open()sqlConnection.Close()sqlConnection = NothingEnd SubWhen I click 100 times on the button the page finally times out with:Timeout expired. The timeout period elapsed prior to obtaining aconnection from the pool. This may have occurred because all pooledconnections were in use and max pool size was reached.Of course I could increase the max pool size but this isn't thesolution to this problem. I wonder what's wrong with my code?According to MSDN, if the connection is closed it's released back intothe pool. Also tried to dispose but nothing helps. It looks like thatit keeps connections and doesn't release them. I'm grateful for anyhints, ideas, suggestions on this problem as I'm very desperate tosolve this.Thanks very much for your time & efforts!Martin
View 5 Replies View RelatedHi
I have seen the threads already in here about connections and SQL Server but I too am having a connection pool problem.
I am explicitly making a connection, creating a command object, executing a datareader then closing the command and then disposing the connection. The connection just prior to the dispose is definately closed.
However when I do an sp_who in SQL Server the connection is still listed. I have a connection timeout of 30 seconds, so I am considering reducing this to 5 seconds but dont wish to. So therefore when a process is called repeatedly instead of using an existing connection in the pool, it thinks that this connection is still active and therefore creates a new connection. Because all of this is in an ascx, I cant code for one connection to stay open for all 30 instances of the control.
This is a problem because I am creating controls at run time and using page.databind and at that point, I exceed the connection pool and therefore the site crashes out to the "SQL Server Timeout" error.
Anyone else seen this?
Hi,
I have recently installed SP2 for SQLServer 2005 and started to have connection pool issues. I have tried to explicitly mention the pool settings in connection string and yet pooling doesn't seem to work. I have one more box with no service packs applied and is pooling is perfect!. Has any one experienced this??
Thank you,
Viswanath Ivatury
HI,
I am using SqlServer2005 as data base for my web application. I am able to connect to the database through DBCP connection pool . Its working fine for 2 user. When ever 2 users do transaction, it works fine. But 3 users do the transaction, its trowning error.Even i increase the pool size the behavior is same.
error:
com.microsoft.sqlserver.jdbc.SQLServerException: Server failed to resume the transaction, desc: 3f00000002.
For a change I wrote a connection pool to access the DB. I am getting the same error. i.e. Its working fine for 2 user and throws error for more than 2 users.
Is there any setting to be made?
Same application is working fine for Oracle10g.
Regrads
Rupesh
I was wondering if someone could help explaining how the SQL Server handles all incoming connections, I and a friend started a discussion about using the connection pool in ADO.NET or not in a specific case.
Usually when creating like an ASP.NET Page it's recommended to use the connection pool, because it optimizes the performance, by using already created connection, so we don't have to recreate the connection all the time. I have always thought that the connection in the connection pool had an open connection on the server. So 5 connections in the connection pool, would be 5 open connections at the server. But after having the discussion with my friend I am not so sure anymore.
Say that I would create a client application (.NET using ADO.NET) that connects to the database and work with that data. If I then have 1.000 clients and each client have a connection pool with 5 connections in it (I think that the default numbers for the connection pool), then there would be like 5.000 open connections on the SQL Server, where most of the connections actually never do anything more than hanging around and waiting... And then the connectionpool is not 1 per client but 1 per connectionstring.
So if my client scenario would access data from 2 different databases, there would actually be 10.000 open connections at the SQL Server. So now I think that there must be a server connection pool or something to handle the connection from the clients. So that there would only be like 10-50 open connections at the server for the 1.000 Clients that was connected.
How is it? Is there 1 open connection in the server for every connection in the connection pool? If that's the case, it would be better for the SQL Server if I don't not use the connection pool in the client, but instead open the connection when we need it, and then close it, and taking that little performance hit every time, to help the performance on the SQL Server.
Best regards
- Magnus
Hi,
I am facing problem in configuring and using connection pooling on tomcat 5.0. I am using JDBC Driver v.1.1 for SQL Server 2005.
Can anybody point me to appropriate samle code or guideline?
Thanks & Regards,
Bhavin P Panchal
client: ado.net 2.0 SqlClient, xp sp 2
server: sql server 2005, win 2k
I have a stored proc eg spProcA which does not start a transaction
If I call this proc from ado.net code without any transaction around it affecting the isolation level, the isolation level within the proc call is read committed, as expected
If I then call the same proc within a System.Transacstion.TransactionScope with a different isolation level eg Serializable, then i get the expected isolation level in the proc.
However, if i retry the proc without any transaction around it, the isolation level is now the same as the TransactionScope, (eg Serializable), and this persists until either the connection pool clears down (either because it becomes dormant or via an explicit ClearAllPools.
I can resolve this problem by setting the isolation level in every proc (or call to every proc), but i wondered if i am missing something more straight forward?
Halo all
I have a problem with "timeout expired. Thei timeout periode elapsed prior to obtaining a connection from the pool. This may have occured because all pooled connections were use and max pool size was reached"
Then i explore and found out that i did not close my SqlDataReader, SqlDataAdapter, SqlCommand or my connection.
But i have a function that return a SqlDataReader.
Is this function will cause a connection problem?
Thanks in advance
Public Function GetDataReader(ByVal strSQL As String, ByVal DBCon As DB.DBConnection) As SqlDataReader Dim MyCommand As SqlCommand = New SqlCommand(strSQL, DBCon.GetConnection())
If DBCon.GetConnection().State = ConnectionState.Closed Then DBCon.GetConnection().Open() End If
Dim dr As SqlDataReader = MyCommand.ExecuteReader()
Return dr
dr.Close()
End Function
This is my code...
public partial class test : System.Web.UI.Page
{protected void Page_Load(object sender, EventArgs e)
{SqlDatabase database = (SqlDatabase)DatabaseFactory.CreateDatabase("ConnectionString");DbCommand command = database.GetSqlStringCommand("SELECT UserName FROM Users WHERE UserID = '6264'");
using (IDataReader reader = database.ExecuteReader(command))
{if (reader.Read())
{lblTest.Text = "test";
}
}
}
}
This is my error:
Server Error in '/' Application.
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.Source Error:
Line 21: //DbCommand command = database.GetStoredProcCommand("CorrUsers_GetByUserId_s");
Line 22: DbCommand command = database.GetSqlStringCommand("SELECT UserName FROM Users WHERE UserID = '6264'");
Line 23: database.ExecuteReader(command);
Line 24: using (IDataReader reader = database.ExecuteReader(command))
Line 25: {Source File: d:webwwwrootchacha078dev.cha.toplingo.com est.aspx.cs Line: 23 Stack Trace:
[InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.]
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +1261381
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
Microsoft.Practices.EnterpriseLibrary.Data.Database.GetNewOpenConnection() +195
Microsoft.Practices.EnterpriseLibrary.Data.Database.GetOpenConnection(Boolean disposeInnerConnection) +106
Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteReader(DbCommand command) +62
test.Page_Load(Object sender, EventArgs e) in d:webwwwrootchacha078dev.cha.toplingo.com est.aspx.cs:23
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436
Any help with this matter would be very much appreciated.
Thank you for your time.
Sincerely,
Jeffrey Pham
Server Error in '/' Application.
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.]
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +1188873
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +413
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
DataCaoZuo.Manage_ResultTB_Caozuo(String comstr) +145
Cls_UserManage.GetAllUserList() +18
Index.Page_Load(Object sender, EventArgs e) +83
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
Ok bear with me here :). I have a server that is getting about 1000000 hits per day with about 10,000 unique vistors. For the past 2 months I have been revamping my code trying to deal with the increase in traffic. I have 2 boxes, one for the website, and one for the SQL. They are connected through a secure backlink so that I dont have to worry about encrypting the data. So the problem started when I updated the MDAC components a few weeks ago. I started getting these freaking timeout errors, they are up to about 1000 errors per hour. I have been monitoring the connection pooling using the system monitor for about a week and have noticed that I am not maxing out the pooling but I am still dropping connections. I went into the web.config and turned my max connections to 1000. Unfortunately this didn't even put a dent in the problem. It doesn't matter if I have 12 or 212 open connections it still drops them. I am at my wits end with trying to debug this problem. I am wondering if anyone else has had similiar problems recently. Also on a side note I have checked all my connections to make sure that I am closing them. Not only do I close my datareaders but I also set them to nothing. In addition to closing and reseting my datareaders I am also disposing and reseting my connection objects as well as closing them. Any help would be greatly appreciated.
Thanks,
Daniel Christoffersen
Hi to everyone,
I'm facing a problem that drives me crazy. I've a web application that has the following problem. When I test the application on my developement machine all runs fine, but when I put into production server there is a problem in connection pooling. Look at the following image, the blue line is the number of connection in the pool and the violet line is the number of connection reclaimed. From the image it is clear that connection are returned on the pool only in block, maybe when the garbage collection pass and reclaim the object. The strange thing is that on my developement machine all is good, and also I'm using Enterprise Library and the connection are managed internally.- Thanks to everyone for any help.
1) What is the use of pooling actually?
I have an online application using SQL server, where I can check the connection pool from, SQL Server Enterprise Manager->Microsoft SQL Server->SQL Server Group->LOCAL->Management->Current Activity->Process Info.
2) In the connection pool, when I log into my system, a connection is made as I run query using stored procedure thus making the process available in the connection pool. Now when I am done and log out of the system, does the process suppose to stay there or not (the connection closed) and making it disappear from the pool?
I read from some forum that pooling is a good thing as it make accesing data faster.
HiI have written the following function public System.Data.SqlClient.SqlDataReader ExcuteReader(string strQuery, string strConnection) { System.Data.SqlClient.SqlCommand myCommand; System.Data.SqlClient.SqlDataReader myReader; myCommand = new System.Data.SqlClient.SqlCommand(strQuery, new System.Data.SqlClient.SqlConnection(strConnection)); myCommand.Connection.Open(); myReader = myCommand.ExecuteReader(); return myReader; }to return a datareader for me but right now I am facing the problem that it seems this function isn't closing the connection by itself which is resulting in an error saying "Timeout expired. The timeout period elapsed prior to
obtaining a connection from the pool. This may have occurred because
all pooled connections were in use and max pool size was reached" and if I close it manually I will lose the data in the readerso are there any suggestions of what I should do?thank you