RE: Urgent problem : Plz help

From: Khan, Muhammad S <>
Date: Thu, 19 Mar 2009 14:34:52 -0400
Message-ID: <>

Thanks folks for your responses.

We finally find out that all the new sessions were coming out of one of the application servers that was supposed to submit some jobs at the database server but somehow it was establishing connections in infinite loop. That box is unmanaged so we are good for now.

Appreciate your help.


Muhammad S. Khan
Sr. Database Administrator

-----Original Message-----

[] On Behalf Of Lyndon Tiu Sent: Thursday, March 19, 2009 10:53 MUHAMMAD To:
Subject: Re: Urgent problem : Plz help

  1. Connection pooling.

You can either have connection pooling at the DB or at the application level.

You already mentioned you do not use connection pooling at the DB level.

Looks like an application connecting to your database is not using connection pooling either. Looks like it is opening a new connection for every query. It also looks like it is not closing the connections properly after use.

It is good database coding practice to be using connection pooling at the application level. That way, only a set number of connections are opened and are kept open and reused, reducing the load on resources. This also speeds up queries since connections don't have to be opened for each query.

Make sure to communicate that to the app developers.

2) One way to check who is opening all the connections is to use the OS command:

netstat -an

Try to find all the ip addresses connecting to the database server and track it down and find your culprit.


Lyndon Tiu

-- Received on Thu Mar 19 2009 - 13:34:52 CDT

Original text of this message