RE: JDBC Connection Pool Theory ??
Are there any pools that are for JDK1.1?
RE: JDBC Connection Pool Theory ??
The most expensive part of working with databases is instanciating connections. so really it makes alot of difference to have those instanciated from the beginning. The reasons for using connection pooling mechanism are many... I cant remember a single reason why someone should not use one. Just the fact that it simplifies the access to the database from your servlets is big enough reason. It´s very simple to install and use. the one I recomend is free software from www.bitmechanic.com hope it helps, reynir hubner [EMAIL PROTECTED] cto -Original Message- From: Jonathan Eric Miller [mailto:[EMAIL PROTECTED]] Sent: 24. september 2001 15:55 To: [EMAIL PROTECTED] Subject: Re: JDBC Connection Pool Theory ?? What I want to know is how much of a difference connection pooling really makes? My application isn't taking a lot of hits, so, maybe if it was, I would notice the difference, but, right now, I see no need to use connection pooling. Jon - Original Message - From: "Gustavo Saramago" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 21, 2001 6:23 AM Subject: Re: JDBC Connection Pool Theory ?? > It's hard to imagine a real world application without database access. The > JDBC spec delegate the responsability for connection pool implementation to > th JDBC driver vendor. This result in proprietary implementations of pools > that reduce code portability. > > General solutions like Poolman are good choices. It's a light piece of code > as Jon said, but I have saw people having problems using it with Tomcat. Our > lives would be mutch easier if the JDBC spec had defined a standard > connection pool. > > Why Tomcat do not implement a connection pool? Nothing aganist Poolman, but > standards are welcome. > > - Original Message - > From: "Jon Shoberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 21, 2001 12:48 AM > 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 :) > > > > Jon > > > > -Original Message- > > From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, September 20, 2001 10:32 PM > > To: [EMAIL PROTECTED] > > 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...). > > > > --V. > > > > > > - Original Message - > > From: "Jon Shoberg" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > 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, > > low > > > 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 > > > > > > > > >
Re: JDBC Connection Pool Theory ??
Hi Jon, [EMAIL PROTECTED] said: : What I want to know is how much of a difference connection pooling : really makes? My application isn't taking a lot of hits, so, maybe if : it was, I would notice the difference, but, right now, I see no need : to use connection pooling. : Jon Part of the reason behind connection pooling is simply that building a connection to the database can be quite expensive (in terms of time), so in order to make your application appear more responsive, having a pool of pre-built connections which you can use right away makes the overall response time that much shorter, since each request isn't going through the effort of building (and, at the end, tearing down) the database connection. It's entirely possible that you feel that the responsiveness of your application is adequate at the moment, if you're not getting a lot of traffic, that's certainly reasonable. It's just that the facility is there, should your application's user base grow to the point where you need it. No one's holding a gun to your head and insisting that you should use it. Brendan -- Brendan McKennaEmail: [EMAIL PROTECTED] Development Strategist Phone: +353-61-338177 Taringold Ltd. Fax: +353-61-338065
Re: JDBC Connection Pool Theory ??
You could also probably just store the database connection in a session variable. That way, the connection is only setup after the user first authenticates instead of at each page request. Jon - Original Message - From: "Mihai Gheorghiu" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 24, 2001 10:31 AM Subject: Re: JDBC Connection Pool Theory ?? > Thank you very much. > Aside from lower speed (open a db connection every time a servlet requires > it), are there any other inconveniences or risks if not using a connection > pool? > > -Original Message- > From: C. Schlegelmilch <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > Date: Saturday, September 22, 2001 2:20 AM > Subject: Re: JDBC Connection Pool Theory ?? > > > >A pool of a fixed number of connections is generally > >initialized right at startup of the web application. > >From then on in, when a user of a wep app requires a > >connection, it pulls it away form the pool and returns > >it when its done. Because all users of a web app > >effectively share all of the connections of a pool, > >there is never one connection reserved for one user. > >Its generally a better use of resources not to. > > > >But now that I think of it, there is nothing stopping > >you from assigning a user to a connection in a pool. > >That would require some interesting design work to > >make it slick, but its possible. > > > >While this may not solve your current issue, give this > >a try: > > > >http://www.webdevelopersjournal.com/columns/connection_pool.html > > > >The code looks very similar to some of the class > >solutions. > > > > --- Mihai Gheorghiu <[EMAIL PROTECTED]> wrote: > > >I've been looking at some pooling examples and I > >> must admit I'm still not > >> clear whether it is possible to have db connections > >> with the username and > >> password of the web/java user, or the database > >> "sees" n connections with the > >> same username and password generated by the pool > >> manager. I want the > >> web/java usernane and pwd to be passed to the db for > >> logging/signing > >> purposes. Can anyone please point me to some > >> relevant > >> documentation/tutorial? > >> Thank you all. > >> > >> -Original Message- > >> From: C. Schlegelmilch <[EMAIL PROTECTED]> > >> To: [EMAIL PROTECTED] > >> <[EMAIL PROTECTED]> > >> Date: Friday, September 21, 2001 12:19 PM > >> Subject: Re: JDBC Connection Pool Theory ?? > >> > >> > >> >We had our web development class develop their own > >> >software for connection pooling. These are > >> extremely > >> >simple soluitons but they work quite well for the > >> >small to medium traffic they are likely to get. > >> > > >> >They are using "Professional Java Server > >> Programming" > >> >as a reference and it has some interesting sections > >> on > >> >Connection Pooling. This is good if you're only > >> >running a simple application. It was also noted > >> that > >> >this resource did not address any synchronization > >> >issues which is very important (the last thing you > >> >want is two seperate threads getting a reference to > >> >the next free connection at the same time). This > >> is > >> >really the only big gottcha that we found in a > >> simple > >> >implementation. > >> > > >> > --- Jon Shoberg <[EMAIL PROTECTED]> wrote: > > >> >> 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, low > >> >> 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 > >> >> > >> > > >> > >> > >> >Do You Yahoo!? > >> >Get your free @yahoo.co.uk address at > >> http://mail.yahoo.co.uk > >> >or your free @yahoo.ie address at > >> http://mail.yahoo.ie > >> > > > > > >Do You Yahoo!? > >Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk > >or your free @yahoo.ie address at http://mail.yahoo.ie >
Re: JDBC Connection Pool Theory ??
What I want to know is how much of a difference connection pooling really makes? My application isn't taking a lot of hits, so, maybe if it was, I would notice the difference, but, right now, I see no need to use connection pooling. Jon - Original Message - From: "Gustavo Saramago" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 21, 2001 6:23 AM Subject: Re: JDBC Connection Pool Theory ?? > It's hard to imagine a real world application without database access. The > JDBC spec delegate the responsability for connection pool implementation to > th JDBC driver vendor. This result in proprietary implementations of pools > that reduce code portability. > > General solutions like Poolman are good choices. It's a light piece of code > as Jon said, but I have saw people having problems using it with Tomcat. Our > lives would be mutch easier if the JDBC spec had defined a standard > connection pool. > > Why Tomcat do not implement a connection pool? Nothing aganist Poolman, but > standards are welcome. > > - Original Message - > From: "Jon Shoberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 21, 2001 12:48 AM > 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 :) > > > > Jon > > > > -Original Message- > > From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, September 20, 2001 10:32 PM > > To: [EMAIL PROTECTED] > > 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...). > > > > --V. > > > > > > - Original Message - > > From: "Jon Shoberg" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > 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, > > low > > > 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 > > > > > > > > >
Re: JDBC Connection Pool Theory ??
Thank you very much. Aside from lower speed (open a db connection every time a servlet requires it), are there any other inconveniences or risks if not using a connection pool? -Original Message- From: C. Schlegelmilch <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Saturday, September 22, 2001 2:20 AM Subject: Re: JDBC Connection Pool Theory ?? >A pool of a fixed number of connections is generally >initialized right at startup of the web application. >From then on in, when a user of a wep app requires a >connection, it pulls it away form the pool and returns >it when its done. Because all users of a web app >effectively share all of the connections of a pool, >there is never one connection reserved for one user. >Its generally a better use of resources not to. > >But now that I think of it, there is nothing stopping >you from assigning a user to a connection in a pool. >That would require some interesting design work to >make it slick, but its possible. > >While this may not solve your current issue, give this >a try: > >http://www.webdevelopersjournal.com/columns/connection_pool.html > >The code looks very similar to some of the class >solutions. > > --- Mihai Gheorghiu <[EMAIL PROTECTED]> wrote: > >I've been looking at some pooling examples and I >> must admit I'm still not >> clear whether it is possible to have db connections >> with the username and >> password of the web/java user, or the database >> "sees" n connections with the >> same username and password generated by the pool >> manager. I want the >> web/java usernane and pwd to be passed to the db for >> logging/signing >> purposes. Can anyone please point me to some >> relevant >> documentation/tutorial? >> Thank you all. >> >> -Original Message- >> From: C. Schlegelmilch <[EMAIL PROTECTED]> >> To: [EMAIL PROTECTED] >> <[EMAIL PROTECTED]> >> Date: Friday, September 21, 2001 12:19 PM >> Subject: Re: JDBC Connection Pool Theory ?? >> >> >> >We had our web development class develop their own >> >software for connection pooling. These are >> extremely >> >simple soluitons but they work quite well for the >> >small to medium traffic they are likely to get. >> > >> >They are using "Professional Java Server >> Programming" >> >as a reference and it has some interesting sections >> on >> >Connection Pooling. This is good if you're only >> >running a simple application. It was also noted >> that >> >this resource did not address any synchronization >> >issues which is very important (the last thing you >> >want is two seperate threads getting a reference to >> >the next free connection at the same time). This >> is >> >really the only big gottcha that we found in a >> simple >> >implementation. >> > >> > --- Jon Shoberg <[EMAIL PROTECTED]> wrote: > >> >> 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, low >> >> 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 >> >> >> > >> >> >> >Do You Yahoo!? >> >Get your free @yahoo.co.uk address at >> http://mail.yahoo.co.uk >> >or your free @yahoo.ie address at >> http://mail.yahoo.ie >> > > >Do You Yahoo!? >Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk >or your free @yahoo.ie address at http://mail.yahoo.ie
Re: JDBC Connection Pool Theory ??
A pool of a fixed number of connections is generally initialized right at startup of the web application. >From then on in, when a user of a wep app requires a connection, it pulls it away form the pool and returns it when its done. Because all users of a web app effectively share all of the connections of a pool, there is never one connection reserved for one user. Its generally a better use of resources not to. But now that I think of it, there is nothing stopping you from assigning a user to a connection in a pool. That would require some interesting design work to make it slick, but its possible. While this may not solve your current issue, give this a try: http://www.webdevelopersjournal.com/columns/connection_pool.html The code looks very similar to some of the class solutions. --- Mihai Gheorghiu <[EMAIL PROTECTED]> wrote: > I've been looking at some pooling examples and I > must admit I'm still not > clear whether it is possible to have db connections > with the username and > password of the web/java user, or the database > "sees" n connections with the > same username and password generated by the pool > manager. I want the > web/java usernane and pwd to be passed to the db for > logging/signing > purposes. Can anyone please point me to some > relevant > documentation/tutorial? > Thank you all. > > -Original Message- > From: C. Schlegelmilch <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > Date: Friday, September 21, 2001 12:19 PM > Subject: Re: JDBC Connection Pool Theory ?? > > > >We had our web development class develop their own > >software for connection pooling. These are > extremely > >simple soluitons but they work quite well for the > >small to medium traffic they are likely to get. > > > >They are using "Professional Java Server > Programming" > >as a reference and it has some interesting sections > on > >Connection Pooling. This is good if you're only > >running a simple application. It was also noted > that > >this resource did not address any synchronization > >issues which is very important (the last thing you > >want is two seperate threads getting a reference to > >the next free connection at the same time). This > is > >really the only big gottcha that we found in a > simple > >implementation. > > > > --- Jon Shoberg <[EMAIL PROTECTED]> wrote: > > >> 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, low > >> 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 > >> > > > > > >Do You Yahoo!? > >Get your free @yahoo.co.uk address at > http://mail.yahoo.co.uk > >or your free @yahoo.ie address at > http://mail.yahoo.ie > Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
Re: JDBC Connection Pool Theory ??
I've been looking at some pooling examples and I must admit I'm still not clear whether it is possible to have db connections with the username and password of the web/java user, or the database "sees" n connections with the same username and password generated by the pool manager. I want the web/java usernane and pwd to be passed to the db for logging/signing purposes. Can anyone please point me to some relevant documentation/tutorial? Thank you all. -Original Message- From: C. Schlegelmilch <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Friday, September 21, 2001 12:19 PM Subject: Re: JDBC Connection Pool Theory ?? >We had our web development class develop their own >software for connection pooling. These are extremely >simple soluitons but they work quite well for the >small to medium traffic they are likely to get. > >They are using "Professional Java Server Programming" >as a reference and it has some interesting sections on >Connection Pooling. This is good if you're only >running a simple application. It was also noted that >this resource did not address any synchronization >issues which is very important (the last thing you >want is two seperate threads getting a reference to >the next free connection at the same time). This is >really the only big gottcha that we found in a simple >implementation. > > --- Jon Shoberg <[EMAIL PROTECTED]> wrote: > >> 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, low >> 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 >> > > >Do You Yahoo!? >Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk >or your free @yahoo.ie address at http://mail.yahoo.ie
Re: JDBC Connection Pool Theory ??
We had our web development class develop their own software for connection pooling. These are extremely simple soluitons but they work quite well for the small to medium traffic they are likely to get. They are using "Professional Java Server Programming" as a reference and it has some interesting sections on Connection Pooling. This is good if you're only running a simple application. It was also noted that this resource did not address any synchronization issues which is very important (the last thing you want is two seperate threads getting a reference to the next free connection at the same time). This is really the only big gottcha that we found in a simple implementation. --- Jon Shoberg <[EMAIL PROTECTED]> wrote: > > 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, low > 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 > Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
RE: JDBC Connection Pool Theory ??
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 [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 8:49 PM To: [EMAIL PROTECTED] 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 :) Jon -Original Message- From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 10:32 PM To: [EMAIL PROTECTED] 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...). --V. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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, low > 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 > >
RE: JDBC Connection Pool Theory ??
Let me chime in and also say how useful poolman can be. It simplifies your JDBC programming too. It is an open source connection pool utility that can be installed in minutes (at least the 1.4 version was). It can also be used more generally as an object pool if I recall. For those who don't know, see http://www.codestudio.com/. J. Haller -Original Message- From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 8:32 PM To: [EMAIL PROTECTED] 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...). --V. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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, low > 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 > >
Re: JDBC Connection Pool Theory ??
Hi, Anybody are using Poolman with Tomcat 4 ?? it works ?? Roy
Re: JDBC Connection Pool Theory ??
I am currently working on a research project involving comparing the various methods and approaches to database connection pooling - my website has a few links to some vendor's sites and some technical articles you may find useful. You can get to it at http://www2.gvsu.edu/~millerjr/ Hope this helps >>> [EMAIL PROTECTED] 9/20/01 10:37:44 PM >>> 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, low 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
RE: JDBC Connection Pool Theory ??
try using the bitmechanics pool, it´s great...we have never had any problems, we are both using it with tomcat 3 and tomcat 4... -r -Original Message- From: Gustavo Saramago [mailto:[EMAIL PROTECTED]] Sent: 21. september 2001 11:24 To: [EMAIL PROTECTED] Subject: Re: JDBC Connection Pool Theory ?? It's hard to imagine a real world application without database access. The JDBC spec delegate the responsability for connection pool implementation to th JDBC driver vendor. This result in proprietary implementations of pools that reduce code portability. General solutions like Poolman are good choices. It's a light piece of code as Jon said, but I have saw people having problems using it with Tomcat. Our lives would be mutch easier if the JDBC spec had defined a standard connection pool. Why Tomcat do not implement a connection pool? Nothing aganist Poolman, but standards are welcome. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 21, 2001 12:48 AM 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 :) > > Jon > > -Original Message- > From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 20, 2001 10:32 PM > To: [EMAIL PROTECTED] > 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...). > > --V. > > > - Original Message - > From: "Jon Shoberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > 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, > low > > 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 > > > > >
Re: JDBC Connection Pool Theory ??
It's hard to imagine a real world application without database access. The JDBC spec delegate the responsability for connection pool implementation to th JDBC driver vendor. This result in proprietary implementations of pools that reduce code portability. General solutions like Poolman are good choices. It's a light piece of code as Jon said, but I have saw people having problems using it with Tomcat. Our lives would be mutch easier if the JDBC spec had defined a standard connection pool. Why Tomcat do not implement a connection pool? Nothing aganist Poolman, but standards are welcome. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 21, 2001 12:48 AM 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 :) > > Jon > > -Original Message- > From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 20, 2001 10:32 PM > To: [EMAIL PROTECTED] > 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...). > > --V. > > > - Original Message - > From: "Jon Shoberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > 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, > low > > 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 > > > > >
RE: JDBC Connection Pool Theory ??
Hello I would like to know if somebody is using the pool of Turbine, used already by tomcat. I am affraid that there is no doc on these classes :| Alexandre
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 :) Jon -Original Message- From: Vladimir Grishchenko [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 10:32 PM To: [EMAIL PROTECTED] 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...). --V. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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, low > 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 > >
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...). --V. - Original Message - From: "Jon Shoberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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, low > 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 > >
