Re: [JDBC] Connection pooling
- From: "Michael Luchs" <mmr-michael@xxxxxxxx>
- Date: Tue, 19 Jul 2005 12:30:27 +0200
Hi,
of course you should only use a tomcat when your app is a webapp. You cant
use the tomcat connection pooling with normal apps.
Regards
Michael
"Arnaud" <pas@xxxxxxxxxx> schrieb im Newsbeitrag
news:dbif6d$cl0$2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi!
>
> Here are a few things I don't understand about connection pooling.
>
> The DBCP API seems to be what I need, but I've read some articles about
> using Tomcat to manage connection pooling rather than doing it by hand.
>
> What I don't understand is that I need a servlet and my app isn't a
> webapp at all.
>
> So what's the advantage to use Tomcat rather than a simple
> PoolingDataSource ? Is it only the ability to set dead connection
> detection (connections we have forget to return to pool) ?
>
> If it is really more interesting, I absolutely don't understand how to
> call the servlet from by app and how to get a ResultSet from it.
>
> Could someone help me please.
>
> TIA
>
> --
> Arnaud
.
- Follow-Ups:
- Re: [JDBC] Connection pooling
- From: Mark Matthews
- Re: [JDBC] Connection pooling
- From: arN
- Re: [JDBC] Connection pooling
- References:
- [JDBC] Connection pooling
- From: Arnaud
- [JDBC] Connection pooling
- Prev by Date: [JDBC] Connection pooling
- Next by Date: Re: hsqldb transfer tool
- Previous by thread: [JDBC] Connection pooling
- Next by thread: Re: [JDBC] Connection pooling
- Index(es):
Relevant Pages
|
|