David, We use DBCP on a mission critical 24 x 7 application - and we have no issues with it.
We started with Tomcat 4.1.12 and are about to go to 4.1.18 - already in development and working fine. When we did our initial investigations, we were able to use DBCP at all the levels possible in server.xml - i.e. within a specific context, as a DefaultContext, and as a GlobalNamingResource. What we do not do is place any reference to our DBCP resource in a web.xml file. Not only is it unnecessary if defined in server.xml, but it is my belief that the web.xml resource replaces the server.xml resource - and as you do not give the driver name in a web.xml resource, you get a null value. -----Original Message----- From: David Durst [mailto:[EMAIL PROTECTED]] Sent: Montag, 13. J�nner 2003 11:30 To: [EMAIL PROTECTED] Subject: Re: javax.naming.NameNotFoundException: Name admin is not bound in this Context > Sounds like you don't have the appropiate driver loaded or you have > incorrectly specified your pgsql driver in server.xml. Double check the > values. I make that mistake alot. I have gotten that answer like 10 times now :( I have the correct driver specified :) I must have because I had this all working up until about 30 minutes ago. I have the jar in both common/lib/ and sfadmin/WEB-INF/lib I am starting to think the whole DBCP thing is very unstable. -- 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]>
