Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

What is the difference between Connection Pool and data source?

Answer Posted / jaydeb chakraborty

Applications access a data source using a connection and
access Databases via DataSource objects.

A DataSource has a set of properties that identify and
describe the real world data source that it represents.
These properties include information such as the location
of the database server, the name of the database, the
network protocol to use to communicate with the server, and
so on.
DataSource object can be thought of as a factory for
connections to the particular data source that the
DataSource instance represents. In a basic DataSource
implementation, a call to the getConnection method returns
a connection object that is a physical connection to the
data source.

DataSource objects that implement connection pooling also
produce a connection to the particular data source that the
DataSource class represents. The connection object that the
getConnection method returns is a handle to a
PooledConnection object rather than being a physical
connection. An application uses the connection object in
the same way that it uses a connection. Connection pooling
has no effect on application code except that a pooled
connection, like all connections, should always be
explicitly closed. When an application closes a connection
that is pooled, the connection is returned to a pool of
reusable connections. The next time getConnection is
called, a handle to one of these pooled connections will be
returned if one is available. Because connection pooling
avoids creating a new physical connection every time one is
requested, it can help applications run significantly
faster.

Is This Answer Correct ?    14 Yes 2 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Can I still use the default connection factories supported in weblogic release 5.1? : BEA Weblogic

1029


How does a server find out server unavailability?

964


What is the purpose of t3 in weblogic server?

961


What is meant by session replication?

1017


Is it possible to send or receive a message from within a message listener? : BEA Weblogic

911


Explain about cluster heart beats?

999


What are stubs and how do they function in a web logic cluster?

1051


Tell me how is the security handled in web logic j2ee connector architecture?

937


What precautions should I take when I use blocking receive() calls? : BEA Weblogic

981


In a web logic server what is the domain?

1008


What are the advantages and disadvantages of node manager?

1040


In Future how the role of WEBLOGIC in realtime ?

2021


How to make a managed server ?

1095


An instance of stateful session ejb when accessed simultaneously from more than one clients on same vm results in remoteexception or ejbexception. In case the client is a servlet thread, which of the techniques can be used to avoid remoteexception/ejbexception? : BEA Weblogic

988


Is it ok to add new sessions and subscribers to a queue or topic connection once it has been started? : BEA Weblogic

1136