Return-Path: 
 <ibatis-user-java-return-2636-apmail-incubator-ibatis-user-java-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ibatis-user-java-archive@www.apache.org
Received: (qmail 68869 invoked from network); 6 Jun 2005 19:24:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 6 Jun 2005 19:24:43 -0000
Received: (qmail 33063 invoked by uid 500); 6 Jun 2005 19:24:41 -0000
Delivered-To: apmail-incubator-ibatis-user-java-archive@incubator.apache.org
Received: (qmail 33046 invoked by uid 500); 6 Jun 2005 19:24:41 -0000
Mailing-List: contact ibatis-user-java-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ibatis-user-java@incubator.apache.org
List-Help: <mailto:ibatis-user-java-help@incubator.apache.org>
List-Unsubscribe: <mailto:ibatis-user-java-unsubscribe@incubator.apache.org>
List-Post: <mailto:ibatis-user-java@incubator.apache.org>
List-Id: <ibatis-user-java.incubator.apache.org>
Delivered-To: mailing list ibatis-user-java@incubator.apache.org
Received: (qmail 33032 invoked by uid 99); 6 Jun 2005 19:24:41 -0000
X-ASF-Spam-Status: No, hits=1.7 required=10.0
	tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,MSGID_FROM_MTA_HEADER,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of vi_am@hotmail.com designates
 65.54.247.6 as permitted sender)
Received: from bay2-f6.bay2.hotmail.com (HELO hotmail.com) (65.54.247.6)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 06 Jun 2005 12:24:38 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 6 Jun 2005 12:24:27 -0700
Message-ID: <BAY2-F6A3CB9116C7138C65AB9383FB0@phx.gbl>
Received: from 128.3.12.142 by by2fd.bay2.hotmail.msn.com with HTTP;
	Mon, 06 Jun 2005 19:24:27 GMT
X-Originating-IP: [128.3.12.142]
X-Originating-Email: [vi_am@hotmail.com]
X-Sender: vi_am@hotmail.com
From: "vi am" <vi_am@hotmail.com>
To: ibatis-user-java@incubator.apache.org
Cc: vi_am@hotmail.com
Bcc: 
Subject: Connection leak
Date: Mon, 06 Jun 2005 15:24:27 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 06 Jun 2005 19:24:27.0584 (UTC)
 FILETIME=[5AE6C400:01C56ACD]
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

I am evaluating iBATIS.   How can we close connections to avoid connection 
leak?   Are the connections are automatically closed?.... couldn't find this 
anywhere in the documentation.

The following SQL statement shows connections getting incremented for every 
JSP page access.

******************************************
select program, MACHINE, status, schemaname, count(*)
from v$session
where schemaname = 'MY_SCHEMA'
and   status <> 'KILLED'
group by program, machine, status, schemaname;
******************************************

Development environment:   Tomcat 4.1.30,  Oracle 8i,  iBATIS for Java SQL 
Mapper version 2.0  (no DAO just yet),

Here is part of the sql-map-config.xml  file:

******************************************
<transactionManager type="JDBC">
  <dataSource type="DBCP">
    <property name="JDBC.Driver" value="${driver}" />
    <property name="JDBC.ConnectionURL" value="${url}" />
    <property name="JDBC.Username" value="${username}" />
    <property name="JDBC.Password" value="${password}" />
<property name="JDBC.DefaultAutoCommit" value="true" />
    <property name="Pool.MaximumActiveConnections" value="3" />
    <property name="Pool.MaximumIdleConnections" value="2" />
    <property name="Pool.MaximumWait" value="1000" />
  </dataSource>
</transactionManager>
******************************************

Or,  do I have to use  DAO  or  Spring framework to close the connections 
automatically?

Thank you.