Monitoring number of connections

Monitoring number of connections

Postby cp_Volker » Mon 30 May 2011 08:18

Hello,

some weeks ago we have upgraded our ASP.NET application to NET 4.0 and Devart version 6.10.135. Since that time our productive system runs out of connections 1 time per day. We have increased the connection pool (Max Pool Size=300) but this defers only the effect.
Is there any way to monitor the number of concurrently used connections on a productive system? We don't want to use dbMonitor because this tool would slow down the system too much and this will not be accepted by the users.

Thank you for your help.

Best Regards,
Volker
cp_Volker
 
Posts: 3
Joined: Thu 10 Dec 2009 08:14

Re: Monitoring number of connections

Postby Shalex » Wed 01 Jun 2011 08:07

cp_Volker wrote:some weeks ago we have upgraded our ASP.NET application to NET 4.0 and Devart version 6.10.135. Since that time our productive system runs out of connections 1 time per day. We have increased the connection pool (Max Pool Size=300) but this defers only the effect.

1. Are you calling connection.Close() in your code to put connections back to the pool? (DataContext and ObjectContext usually open/close connection on their own).
2. Describe your approach. If possible, send us a small test project with the corresponding DDL/DML script to reproduce the issue in our environment.
cp_Volker wrote:Is there any way to monitor the number of concurrently used connections on a productive system? We don't want to use dbMonitor because this tool would slow down the system too much and this will not be accepted by the users.

1. We recommend using dbMonitor. It allows to monitor local and remote applications.
2. Why have you decided that dbMonitor would slow down the system too much?
Shalex
Devart Team
 
Posts: 7377
Joined: Thu 14 Aug 2008 12:44

Re: Monitoring number of connections

Postby cp_Volker » Wed 01 Jun 2011 15:54

Hello,

we don't open and close the connections explicitly. Usually we instantiate an ObjectContext within an Using directive so that it is disposed after usage and the connection is returned to the pool.
Regrettably, we are unable to isolate the problem in our code so it's not possible to send you a test project with which the behavior can be reproduced.
Our intention was to watch the connections to see if and when the number of connections in the pool increase.
Ok, according to your recommendation we will try to monitor the connections with dbMonitor.

Thank you for your quick response.

Best Regards
Volker
cp_Volker
 
Posts: 3
Joined: Thu 10 Dec 2009 08:14


Return to dotConnect for Oracle