tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haller, Joe" <>
Subject RE: JDBC Connection Pool Theory ??
Date Fri, 21 Sep 2001 16:04:26 GMT
I did experience an issue here.

When I placed my poolman.props file in the /webapp/WEB-INF/lib/
directory (along with the poolman.jar file), poolman was not
able to find the file.  

While Tomcat 4.0 automatically includes any .jar files in the 
/WEB-INF/lib/ in the class path, apparently it does not include
the directory itself in the classpath.  My solution was to 
unzip the poolman classes into /webapp/WEB-INF/classes and also
place the poolman.props file at this location.

Everything worked fine from there.

J. Haller

-----Original Message-----
From: Jon Shoberg []
Sent: Thursday, September 20, 2001 8:49 PM
Subject: RE: JDBC Connection Pool Theory ??

One of the issues would be someting that has been crossing the lists
recently.  Few people have posted that poolman is broken under TC4.0.  I'll
have to try it myself and see. However, I like to do my own plumbing :)


-----Original Message-----
From: Vladimir Grishchenko []
Sent: Thursday, September 20, 2001 10:32 PM
Subject: Re: JDBC Connection Pool Theory ??

"Professional Java server programming " from WROX had a chapter about it, as
far as I remember. I can't call it a "comprehensive study", but it had some
meaningful explanations.

What's wrong with poolman btw? IMHO it is as simple as it gets, your
application doesn't even know it deals with pooled connections. Portable? As
portable as Java itself.

 My philosophy on such things is take it if it's available and concentrate
on your application domain issues and not the plumbing (plumbing in good
sense here...).


----- Original Message -----
From: "Jon Shoberg" <>
To: <>
Sent: Thursday, September 20, 2001 7:37 PM
Subject: JDBC Connection Pool Theory ??

> Can anyone suggest or point to readings on JDBC connection pool theory?
> Something that covers how a pool is implemented, best case / worst case
> scenarios, tips and traps.
> My next web application is looking to be very database (mysql) intensive.
> I would like a pooling mechanism that is VERY simple to use, VERY light,
> overhead, and portable.  Having looked at packages such as poolman, I
> decided I need to learn a bit more about JDBC and pooling in general.  Any
> thoughts ?
> Jon

View raw message