63 lines
5.3 KiB
HTML
63 lines
5.3 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="JDBC object pooling" />
|
||
|
|
<meta name="abstract" content="Object pooling is the most common topic to come up when discussing Java Database Connectivity (JDBC) and performance. Since many objects used in JDBC are expensive to create such as Connection, Statement, and ResultSet objects, significant performance benefits can be achieved by reusing these objects instead of creating every time you need them." />
|
||
|
|
<meta name="description" content="Object pooling is the most common topic to come up when discussing Java Database Connectivity (JDBC) and performance. Since many objects used in JDBC are expensive to create such as Connection, Statement, and ResultSet objects, significant performance benefits can be achieved by reusing these objects instead of creating every time you need them." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="jdbc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="poolwdts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="poolprop.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="poolstat.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="poolnods.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="jdbcpool" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>JDBC object pooling</title>
|
||
|
|
</head>
|
||
|
|
<body id="jdbcpool"><a name="jdbcpool"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">JDBC object pooling</h1>
|
||
|
|
<div><p>Object pooling is the most common topic to come up when discussing Java™ Database
|
||
|
|
Connectivity (JDBC) and performance. Since many objects used in JDBC are expensive
|
||
|
|
to create such as Connection, Statement, and ResultSet objects, significant
|
||
|
|
performance benefits can be achieved by reusing these objects instead of creating
|
||
|
|
every time you need them.</p>
|
||
|
|
<p>Many applications already handle object pooling on your behalf. For example, WebSphere<sup>®</sup> has
|
||
|
|
extensive support for pooling JDBC objects and allows you to control how the
|
||
|
|
pool is managed. Because of this, you can get the functionality you want without
|
||
|
|
being concerned about your own pooling mechanisms. However, when the support
|
||
|
|
is not provided, you must find a solution for all but trivial applications.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="poolwdts.htm">Use DataSource support for object pooling</a></strong><br />
|
||
|
|
You can use DataSources to have multiple applications share a common configuration for accessing a database. This is accomplished by having each application reference the same DataSource name.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="poolprop.htm">ConnectionPoolDataSource properties</a></strong><br />
|
||
|
|
You can configure the ConnectionPoolDataSource interface by using the set of properties that it provides.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="poolstat.htm">DataSource-based statement pooling</a></strong><br />
|
||
|
|
The maxStatements property, available on the UDBConnectionPoolDataSource interface, allows for statement pooling within the connection pool. Statement pooling only has an effect on PreparedStatements and CallableStatements. Statement objects are not pooled.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="poolnods.htm">Build your own connection pooling</a></strong><br />
|
||
|
|
You can develop your own connection and statement pooling without requiring support for DataSources or relying on another product.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="jdbc.htm" title="The IBM Developer Kit for Java JDBC driver, also known as the "native" driver, provides programmatic access to iSeries database files. Using the Java Database Connectivity (JDBC) API, applications written in the Java language can access JDBC database functions with embedded Structured Query Language (SQL), run SQL statements, retrieve results, and propagate changes back to the database. The JDBC API can also be used to interact with multiple data sources in a distributed, heterogeneous environment.">Access your iSeries database with the IBM Developer Kit for Java JDBC driver</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|