I'll second that statement. Where I use it via straight jdbc, I've never, and I repeat never, heard about anyone having a negative experience with. Or even "ok" experiences.
--mikej -=----- mike jackson [EMAIL PROTECTED] > -----Original Message----- > From: Iain Sanderson [mailto:sande010@;mc.duke.edu] > Sent: Tuesday, October 29, 2002 4:58 PM > To: Tomcat Users List > Subject: RE: DBCP Woes! > > > > Neal, > > I use Poolman and have found it excellent. A testimony to it's usefulness > is that folk are still recommending it 9 months after its > developer stopped > supporting it and issued the final 2.1b release. > > You'll find that Poolman's connection code is near identical to that which > you've shown, so your change to Poolman will hardly require any > "investment". > > Your NamingException is may be related to a JNDI naming resource. Check > your JNDI.properties file if there is one. > > Iain. > > > > > > "neal" <[EMAIL PROTECTED]> on 10/29/2002 08:36:02 PM > > Please respond to "Tomcat Users List" <[EMAIL PROTECTED]> > > To: "Tomcat Users List" <[EMAIL PROTECTED]> > cc: > > Subject: RE: DBCP Woes! > > > Oh yeah, and this is the source code for creating a connection: > > protected Connection getConnection() throws NamingException, > SQLException, Exception { > this.CONTEXT = new InitialContext(); > Connection conn = null; > if(this.CONTEXT == null ) throw new Exception("Context needed to > establish conection"); > DataSource ds = (DataSource)CONTEXT.lookup("java:comp/env/jdbc/" + > this.DATABASE); > > if (ds != null) { > conn = ds.getConnection(); > }else{ > return null; > } > return conn; > } > > So it would appear it is blowing up on the line where its attempting to > create datasource. I read another Deja post not too long ago > where someone > was saying that this error is often caused by not having the right context > path reference in the code for creating a Datasource. Someone else said > that you must define your datasource via the web.xml and then its > avail for > reference. BUT, why was it working before (and why is it still working on > my laptop) with out the web.xml reference, and with these exact context > paths? > > So confusing. :( > > Neal > > -----Original Message----- > From: neal [mailto:nealcabage@;yahoo.com] > Sent: Tuesday, October 29, 2002 5:16 PM > To: Tomcat Users List > Subject: RE: DBCP Woes! > > > My setup? I'm using MySQL 3.23 and the latest version of (don't > recall the > number) Connector/J for my driver. This is of course all sitting inside > tomcat 4.0.4. I have manually installed the DBCP, collections > and whatever > other support classes I needed for DBCP. > > I have configured DBCP via my server.xml file as such (below). When I was > recieving the error from (org.hsql) that was because I was also attempting > to creating a reference to the resource within my web.xml file. I have > since removed it and that error has ceased. The error I am currently > experiencing (javax.naming.NameNotFoundException: Name jdbc is > not bound in > this Context) was happening last night. *Seemed* to spontaneously got > away, > then this morning I loaded a few classes and rebooted and it > started again. > I have since removed those classes but the error is persisting. > > Its worth noting that I can still obtain connections directly > through JDBC, > without the use of DBCP, no problem. > > Please let me know if you can think of anything!!!! > > Thanks! > Neal > > > <Context path="" docBase="" debug="5"> > > <Logger className="org.apache.catalina.logger.FileLogger" > directory="logs" prefix="dbcp_" suffix=".log" > timestamp="true" /> > > <Resource name="jdbc/hotel" auth="Container" > type="javax.sql.DataSource" > /> > <ResourceParams name="jdbc/hotel"> > <parameter> > <name>factory</name> > <value>org.apache.commons.dbcp.BasicDataSourceFactory</value> > </parameter> > <parameter> > <name>maxActive</name> > <value>100</value> > </parameter> > <parameter> > <name>maxIdle</name> > <value>30000</value> > </parameter> > <parameter> > <name>maxWait</name> > <value>100</value> > </parameter> > <parameter> > <name>username</name> > <value>xxxxx</value> > </parameter> > <parameter> > <name>password</name> > <value>xxxxx</value> > </parameter> > <parameter> > <name>driverClassName</name> > <value>com.mysql.jdbc.Driver</value> > </parameter> > <parameter> > <name>url</name> > <value>jdbc:mysql:///hotel</value> > </parameter> > <!-- > <parameter> > <name>removeAbandoned</name> > <value>true</value> > </parameter> > <parameter> > <name>removeAbandonedTimeout</name> > <value>30</value> > </parameter> > <parameter> > <name>logAbandoned</name> > <value>true</value> > </parameter> > --> > </ResourceParams> > > </Context> > > -----Original Message----- > From: micael [mailto:caraunltd@;harbornet.com] > Sent: Tuesday, October 29, 2002 4:06 PM > To: Tomcat Users List > Subject: RE: DBCP Woes! > > > I don't know your setup at all, neal, but this is a hypersonic database > reference. What is your setup? > > At 04:31 PM 10/29/2002 -0800, you wrote: > >I considered poolman but it doesn't look like its supported or even > >available from the website to download anymore. Is this the > case? I have > >heard good things about it. > > > >Don't suppose you understand this JDBC conext binding error, do you? > > > >Thanks. > >Neal > > > > > >-----Original Message----- > >From: Mike Jackson [mailto:mjackson@;cdi-hq.com] > >Sent: Tuesday, October 29, 2002 3:25 PM > >To: Tomcat Users List > >Subject: RE: DBCP Woes! > > > > > >Poolman works nicely, I have little to no problems with it. Then again > >I haven't used DBCP. But you'd still have had the exhasted connections > >problem with poolman. > > > >--mikej > >-=----- > >mike jackson > >[EMAIL PROTECTED] > > > > > -----Original Message----- > > > From: neal [mailto:nealcabage@;yahoo.com] > > > Sent: Tuesday, October 29, 2002 4:22 PM > > > To: Tomcat Users List > > > Subject: RE: DBCP Woes! > > > > > > > > > Now I have some other strange error related to accessing my > > > database. Ever > > > since I started messing with thsi stuff my conneciton to my > dB has been > > > flakey at best. Sometimes it works ... sometimes it doesn't. > > > > > > javax.naming.NamingException: Exception creating DataSource: > > > org.hsql.jdbcDriver > > > > > > I don't even know where this class is defined or called!!! > > > > > > >:( > > > > > > Neal > > > > > > > > > > > > > > > Still having DBCP problems. > > > > > > I ensured that all my connections, statements, and resulset objects > > > are being properly released when using DBCP for connection pooling. > I've > > > enabled recoverAbandoned. It seems that yes I did have some > > > connection pool > > > leaking, > > > but that has since been resolved. But I still get this message > > > (along with > > > a > > > failure) from time to time. Does anyone know why? > > > > > > javax.naming.NameNotFoundException: Name jdbc is not bound in this > Context > > > > > > This is a different message than I was getting when I was having > problems > > > with the DBCP pool being exhausted. > > > > > > Thanks! > > > Neal > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > > > For additional commands, e-mail: > > > <mailto:tomcat-user-help@;jakarta.apache.org> > > > > > > > > > -- > > > To unsubscribe, e-mail: > ><mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > >For additional commands, e-mail: > ><mailto:tomcat-user-help@;jakarta.apache.org> > > > > > > > >-- > >To unsubscribe, e-mail: > ><mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > >For additional commands, e-mail: > ><mailto:tomcat-user-help@;jakarta.apache.org> > > > > > >-- > >To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > >For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > Micael > > ------------------------------------------------------- > > This electronic mail transmission and any accompanying documents contain > information belonging to the sender which may be confidential and legally > privileged. This information is intended only for the use of the > individual or entity to whom this electronic mail transmission was sent as > indicated above. If you are not the intended recipient, any disclosure, > copying, distribution, or action taken in reliance on the contents of the > information contained in this transmission is strictly prohibited. If you > have received this transmission in error, please delete the > message. Thank > you > > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:tomcat-user-help@;jakarta.apache.org> > > > -- > To unsubscribe, e-mail: < > mailto:tomcat-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: < > mailto:tomcat-user-help@;jakarta.apache.org> > > > > > > > > > > -- > To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
