Ok, now I'm even more stumped... I decided to try Tomcat's conn pooling before poolman, since in the documentation it says you can configure a validationQuery which I set up as:
<parameter> <name>validationQuery</name> <value>SELECT 'CRAP' FROM DUAL</value> </parameter> The connection pooling works great as long as no connections are killed. Yet, still, when the connections are manually killed, the pooling breaks and you can no longer get a connection. Tomcat reports the error as: java.sql.SQLException: ORA-01012: not logged on I'm starting to think that no matter what ConnectionPooling implementation I try I'm going to run into the same type of error? TIA for any other suggestions (other than don't have your DBA decide she just wants to kill any open connections every morning when she gets into work... sad I know... but that's what she does) On Tuesday, August 27, 2002, 12:53:03 PM, Andrew wrote: AS> Hi Rick, AS> My understanding is that people still successfully use Poolman in AS> production environments. However, I would be worried about using any AS> product that will likely never be updated. Over the weekend, I migrated AS> one of my apps from Poolman to Tomcat 4.1.9 connection pooling (which AS> uses commons-dbcp). Flakiness that I had experienced with Poolman AS> (probably due to a mis-configuration problem that I couldn't pinpoint) AS> seemed to vanish using Tomcat, and as an added bonus, I was able to rid AS> myself of a configuration file! Performance seems just as good, and I AS> have the piece of mind of knowing that I'm using a codebase that is AS> evolving and will be updated. It's super easy to set up using the AS> documentation at: AS> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html AS> And yes it does provide, as an option, the ability to validate AS> connections. This is mentioned in the documentation. AS> There is one small typo in the configuration information though. Where AS> it says: AS> <parameter> AS> <name>user</name> AS> <value>dbusername</value> AS> </parameter> AS> should actually be: AS> <parameter> AS> <name>username</name> AS> <value>dbusername</value> AS> </parameter> AS> Andrew AS> 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]> >> AS> -- AS> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> AS> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Rick mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
