Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <1375135641.36041267461965853.JavaMail.jira@brutus.apache.org>
Date: Mon, 1 Mar 2010 16:46:05 +0000 (UTC)
From: "Gustavo Huff Mauch (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (DBCP-219) how to kill a connection from the
 connection pool without shutting down the connection pool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DBCP-219?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

Gustavo Huff Mauch updated DBCP-219:
------------------------------------

    Comment: was deleted

(was: [F=C3=89RIAS] - Estou de f=C3=A9rias! Volto dia 01/03.
Assuntos urgentes tratar com Cl=C3=A9o (ramal 1112).


Periodo de afastamento

Inicio: 13/2/2010
Termino: 27/2/2010

--=20
DATACOM - Mauch=20
=20
DATACOM
Av. Franca, 725 - Porto Alegre, RS - 90230-220
DDR: +55 51 3358 0100
FAX: +55 51 3358 0101
site: http://www.datacom.ind.br
e-mail: <mauch@datacom.ind.br>
)

> how to kill a connection from the connection pool without shutting down t=
he connection pool
> -------------------------------------------------------------------------=
------------------
>
>                 Key: DBCP-219
>                 URL: https://issues.apache.org/jira/browse/DBCP-219
>             Project: Commons Dbcp
>          Issue Type: New Feature
>    Affects Versions: 2.0
>         Environment: Windows, Unix
>            Reporter: Bill Liu
>             Fix For: 2.0
>
>
> Hi:
> This is really not a bug but probably a desired feature and something I a=
m not aware of.
> We use the Apache connection pool in a Servlet environment. We need the f=
eature to kill or close a connection forcefully when it is being used by a =
servlet. The reason can be various: an evil servlet that holds a connection=
 forever, db issue, network issue, etc. How can we do that? I notice that d=
atasource.getConnection() always returns a new connection. How do we keep t=
rack of connections that are being used so we can close them if needed? Cur=
rently we can only kill one at the database side by a DBA.
> Should we write a a util to keep track of connection objects that are bor=
rowed by clients?

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.