Here's two links, these are the one's I've got archived. They
should be latest, unless they've started development again.
But really, I've never had any problems with poolman, so...
http://www.cdi-hq.com/mj/poolman-2.0.4.tar.gz
http://www.cdi-hq.com/mj/poolman-2.1-b1.tar.gz
--mikej
-=-----
mike jackson
[EMAIL PROTECTED]
> -----Original Message-----
> From: neal [mailto:nealcabage@;yahoo.com]
> Sent: Tuesday, October 29, 2002 4:52 PM
> To: Tomcat Users List
> Subject: RE: DBCP Woes!
>
>
> Interesting. Yeah, this error occassionally pops up and ocassionally goes
> away. When its flaring up I can't get any connections via DBCP. But, I
> still can through regular (non-pooled) JDBC. Uuugh.
>
> Maybe I should look at Poolman. Where can you download it from?
>
> Are there many people out there successfully using DBCP? I don't
> know if it
> matters but I'm using 4.0.4 and had to install all the classes myself. It
> didn't come with Tomcat as it curently does in 4.1.
>
> Neal
>
>
> -----Original Message-----
> From: Mike Jackson [mailto:mjackson@;cdi-hq.com]
> Sent: Tuesday, October 29, 2002 3:44 PM
> To: Tomcat Users List
> Subject: RE: DBCP Woes!
>
>
> I don't think anyone's actively working on it anymore, but it's rock solid
> (tm).
> At least with the way that I'm using it.
>
> As for the JDBC thing, it looks like it's the underlying JDBC driver. I
> don't
> know how DBCP works, but I'd imagine that it's not too different from
> Poolman.
> The point is that if there isn't a connection it's going to make
> a new one,
> and
> that error looks like that's probably where it's occuring. The
> error looks
> like
> it can't find the hsql driver, something to do with the name lookup via
> jndi.
> But I'm not an expert on jndi, so I probably can't help you there. If it
> manages
> to make connections fine up to a point then I'd look at a limit in the
> database,
> there could be something that'll only allow up to so many
> connections to be
> created without closing the older ones. But that's just a guess.
>
> If you want to try out poolman I have the .tar.gz's for both the last beta
> and
> the last "release" version. I'd be happy to email them to you if
> you wish.
> And I could even through in an example config xml file (points at oracle).
>
> --mikej
> -=-----
> mike jackson
> [EMAIL PROTECTED]
>
> > -----Original Message-----
> > From: neal [mailto:nealcabage@;yahoo.com]
> > Sent: Tuesday, October 29, 2002 4:32 PM
> > To: Tomcat Users List
> > Subject: RE: DBCP Woes!
> >
> >
> > 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>
>
>
>
> --
> 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>
