Hi Rick,
My understanding is that people still successfully use Poolman in
production environments. However, I would be worried about using any
product that will likely never be updated. Over the weekend, I migrated
one of my apps from Poolman to Tomcat 4.1.9 connection pooling (which
uses commons-dbcp). Flakiness that I had experienced with Poolman
(probably due to a mis-configuration problem that I couldn't pinpoint)
seemed to vanish using Tomcat, and as an added bonus, I was able to rid
myself of a configuration file! Performance seems just as good, and I
have the piece of mind of knowing that I'm using a codebase that is
evolving and will be updated. It's super easy to set up using the
documentation at:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
And yes it does provide, as an option, the ability to validate
connections. This is mentioned in the documentation.
There is one small typo in the configuration information though. Where
it says:
<parameter>
<name>user</name>
<value>dbusername</value>
</parameter>
should actually be:
<parameter>
<name>username</name>
<value>dbusername</value>
</parameter>
Andrew
On Tuesday, August 27, 2002, at 10:23 AM, Rick Reumann wrote:
> On Tuesday, August 27, 2002, 11:10:53 AM, Kevin wrote:
>
> KAS> If you're not concerned about these other errors, then Poolman
> KAS> (if you can still find it) might be a good fit. If I remember
> KAS> correctly, you could specify a SQL statement for it to execute
> KAS> ("select 1 from dual") before allocating a connection from the
> KAS> pool. If it got a SQLException, it would establish a new
> KAS> connection and return that.
>
> That would be perfect! So just a few questions:
>
> 1) Should I be weary of going to with Poolman if it's not being
> supported anymore?
> 2) Does anyone know if the struts or tomcat pooling behaves like
> above (as an option maybe?) where it will check to see if a
> connection is valid before allocating it?
> 3) Drawbacks going wtih poolman over some other solutions?
>
>
> Thanks again!
>
>
>
> --
>
> Rick
> mailto:[EMAIL PROTECTED]
>
>
> --
> To unsubscribe, e-mail: <mailto:struts-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:struts-user-
> [EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
