RE: Tomcat/Struts - DB Conn Pooling

[Jonas Björnerstedt]

I found the Tomcat documentation very helpful:

http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how
to.html

With a little bit of cut and paste, I added pooling to the struts-blank
application (v1.1)

www.bjornerstedt.org/download/Dbtest.zip

My idea was to add an Action that uses foo.DBTest and call this from a
forward in the index.jsp file. The data would be put in an ActionForm. To
illustrate proper Struts design and be useful as a blank application, I
don't think much more should be added. I don't think I have time right now
to do this, but if anyone else is interested

Jonas

> -Original Message-
> From: neal [mailto:[EMAIL PROTECTED]]
> Sent: den 22 augusti 2002 00:46
> To: Struts Users Mailing List
> Subject: RE: Tomcat/Struts - DB Conn Pooling
>
>
> Thanks!
>
> That is a great article on setting up connection pooling directly
> in Tomcat.
>
> So, I see that some people are using Struts, some PoolMan, and some their
> application server (in this case Tomcat) to achieve conn pooling.  I am
> curious to know (a) which is the most popular of these three
> mechanisms? (b)
> why?, and (c) which one is generally regarded as the "best-practice"
> implementation?
>
> Thanks!
>
> Neal
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 2:46 PM
> To: Struts Users Mailing List
> Cc: [EMAIL PROTECTED]
> Subject: Re: Tomcat/Struts - DB Conn Pooling
>
>
>
> This may help you
>
> http://www.midrangeserver.com/mgo/mgo062602-story01.html
>
> Confidencialidade do Correio do Eletrônico***
> Informações confidenciais podem estar contidas nesta mensagem. Se você não
> se encontra na lista de destinatários ou não é o remetente da mesma, você
> não deve copiar ou enviar esta mensagem para ninguém. Neste caso,
> você deve
> destruir e notificar o remetente da mesma. A empresa considera opiniões,
> conclusões e outras informações que não se relacionam com o
> negócio oficial
> da corporação de responsabilidade do usuário do serviço.
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Tomcat/Struts - DB Conn Pooling

[Craig R. McClanahan]

On Wed, 21 Aug 2002, neal wrote:

> Date: Wed, 21 Aug 2002 14:24:24 -0700
> From: neal <[EMAIL PROTECTED]>
> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]>
> To: Struts Users Mailing List <[EMAIL PROTECTED]>
> Subject: RE: Tomcat/Struts - DB Conn Pooling
>
> So, you find the Struts connection pooling to be a little limited?  What
> would you say is the limitation on Struts conn pool?  Is caching the only
> significant limitation or are there others?
>

Caching of what?  Prepared statements?

In 1.1b2, the Struts connection pool class is a wrapper around the
commons-dbcp connection pool.  I'm pretty sure that caching of prepared
statements is already supported -- if it's not now, but is supported by a
future version of commons-dbcp, then it will be easy to swap in the new
JAR later.

FYI, commons-dbcp is also the implementation that Tomcat 4.1 uses for
connection pooling (4.0 used Tyrex, but that causes unending amounts of
grief for many users).

> It sounds like you're saying you prefer Poolman, when possible.  Would you
> say your sentiment is pretty typical of most other users out there?
>

If your app server supports built in connection pooling via JNDI resources
(which will be the case for any J2EE server), I'd recommend using it --
the odds are much higher that the platform vendor has focused on
optimizing the pool's behavior within that server than just plugging in
something generic.

> Thanks!
> Neal
>

Craig


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Tomcat/Struts - DB Conn Pooling

[neal]

Thanks!

That is a great article on setting up connection pooling directly in Tomcat.

So, I see that some people are using Struts, some PoolMan, and some their
application server (in this case Tomcat) to achieve conn pooling.  I am
curious to know (a) which is the most popular of these three mechanisms? (b)
why?, and (c) which one is generally regarded as the "best-practice"
implementation?

Thanks!

Neal


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 2:46 PM
To: Struts Users Mailing List
Cc: [EMAIL PROTECTED]
Subject: Re: Tomcat/Struts - DB Conn Pooling



This may help you

http://www.midrangeserver.com/mgo/mgo062602-story01.html

Confidencialidade do Correio do Eletrônico***
Informações confidenciais podem estar contidas nesta mensagem. Se você não
se encontra na lista de destinatários ou não é o remetente da mesma, você
não deve copiar ou enviar esta mensagem para ninguém. Neste caso, você deve
destruir e notificar o remetente da mesma. A empresa considera opiniões,
conclusões e outras informações que não se relacionam com o negócio oficial
da corporação de responsabilidade do usuário do serviço.


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Tomcat/Struts - DB Conn Pooling

[marcio . miranda]

This may help you

http://www.midrangeserver.com/mgo/mgo062602-story01.html

Confidencialidade do Correio do Eletrônico***
Informações confidenciais podem estar contidas nesta mensagem. Se você não
se encontra na lista de destinatários ou não é o remetente da mesma, você
não deve copiar ou enviar esta mensagem para ninguém. Neste caso, você deve
destruir e notificar o remetente da mesma. A empresa considera opiniões,
conclusões e outras informações que não se relacionam com o negócio oficial
da corporação de responsabilidade do usuário do serviço.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Tomcat/Struts - DB Conn Pooling

[neal]

So, you find the Struts connection pooling to be a little limited?  What
would you say is the limitation on Struts conn pool?  Is caching the only
significant limitation or are there others?

It sounds like you're saying you prefer Poolman, when possible.  Would you
say your sentiment is pretty typical of most other users out there?

Thanks!
Neal


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 12:12 PM
To: [EMAIL PROTECTED]
Subject: RE: Tomcat/Struts - DB Conn Pooling


I've used both the basic connection pooling through struts and have also
implemented poolman lately for some projects.  I liked poolman because I
can do caching with it...



-Original Message-
From: nealcabage [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 3:01 PM
To: struts-user
Subject: Tomcat/Struts - DB Conn Pooling


For those of you out there who have written web apps using Tomcat and
Struts, with JDBC connectivity, what did you use for dB connection
pooling?
I understand that Struts provides some conn pooling? I read somewhere
that
Tomcat might also provide this functionality, though I wonder if they
were
referring to HTTP connection pooling, rather than dB.  Also, I suppose
there
is the possibility of using PoolMan ... or perhaps if a driver (I think
I'll
be using Connect/J for MySQL) offers it.

Could someone please provide a suggestion or some advice?

Thanks in advice.

:)

Neal


--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: Tomcat/Struts - DB Conn Pooling

[wbchmura]

I've used both the basic connection pooling through struts and have also 
implemented poolman lately for some projects.  I liked poolman because I 
can do caching with it...  



-Original Message-
From: nealcabage [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 3:01 PM
To: struts-user
Subject: Tomcat/Struts - DB Conn Pooling


For those of you out there who have written web apps using Tomcat and
Struts, with JDBC connectivity, what did you use for dB connection 
pooling?
I understand that Struts provides some conn pooling? I read somewhere 
that
Tomcat might also provide this functionality, though I wonder if they 
were
referring to HTTP connection pooling, rather than dB.  Also, I suppose 
there
is the possibility of using PoolMan ... or perhaps if a driver (I think 
I'll
be using Connect/J for MySQL) offers it.

Could someone please provide a suggestion or some advice?

Thanks in advice.

:)

Neal


--
To unsubscribe, e-mail:   
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Tomcat/Struts - DB Conn Pooling

[neal]

For those of you out there who have written web apps using Tomcat and
Struts, with JDBC connectivity, what did you use for dB connection pooling?
I understand that Struts provides some conn pooling? I read somewhere that
Tomcat might also provide this functionality, though I wonder if they were
referring to HTTP connection pooling, rather than dB.  Also, I suppose there
is the possibility of using PoolMan ... or perhaps if a driver (I think I'll
be using Connect/J for MySQL) offers it.

Could someone please provide a suggestion or some advice?

Thanks in advice.

:)

Neal


--
To unsubscribe, e-mail:   
For additional commands, e-mail: