Everyone, thanks for the feedback and additional suggestions on "clean
coding" :). I think I'm good to go.
Thanks,
Tony
-Original Message-
From: Len Popp [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 5:25 PM
To: Tomcat Users List
Subject: Re: Suggestions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Len,
Len Popp wrote:
>Connection conn = ds.getConnection();
>try {
>...do something...
>} finally {
>conn.close();
>}
Might I further suggest:
Connection conn = ds.getConnection();
On 10/25/07, Tony Fountain <[EMAIL PROTECTED]> wrote:
> Now, my goal is to utilize connection pooling. Does (a) this
> implementation achieve that and (b) the close statement suffice to
> return the object to the pool and not actually close the connection? Or
> do I also need to set "conn = null;
that should work for you Tony.
I have a similar setup and mine works properly.
-Original Message-
From: Tony Fountain [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 3:59 PM
To: Tomcat Users List
Subject: RE: Suggestions for connection pooling
Ok - I think I have my answer
---Original Message-
From: Tony Fountain [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 2:39 PM
To: Tomcat Users List
Subject: RE: Suggestions for connection pooling
Thanks for the reference. This looks like what I need. Now to go read
up a bit more to grasp the concept.
To
Users List"
Sent: Thursday, October 25, 2007 1:19 PM
Subject: Suggestions for connection pooling
Platform:
Apache Tomcat 5.5.23 running as windows service JVM 1.5.0_12-b04 (Sun)
Windows 2003 Server
We are running software on this platform that we purchased and
integrated into our product. W
Platform:
Apache Tomcat 5.5.23 running as windows service
JVM 1.5.0_12-b04 (Sun)
Windows 2003 Server
We are running software on this platform that we purchased and
integrated into our product. We replaced the default authentication
class of the product with our own implementation. This resulted
