cool. thanks.
At 11:31 AM 2/21/2002 -0500, Matthew Horn wrote: >PoolMan is going away as a separate product; however, a beefed-up version >of it is now in JRun 4 (in Beta now); the lead architect of JRun 4 is the >same guy who created PoolMan. > >PoolMan does come with source code. > >-----Original Message----- >From: Tom Duffy [mailto:[EMAIL PROTECTED]] >Sent: Thursday, February 21, 2002 10:47 AM >To: JRun-Talk >Subject: re: Caching connection > > >Hi Ben, > Does PoolMan come with source code? > >tom > >At 09:47 AM 2/21/2002 -0600, you wrote: > >Even if you are using the jrun database management pool, you will often have > >problems with too many connections. > >As a matter of fact, I think it might be even more pronounced than not using > >a pool, because a close() doesn't necessarily "close" the connection, but > >releases it back to the pool instead. We have had times where we were sure > >we were releasing connections, but still new connections were being opened. > >With the jrun native database management pool, there is no way to set the > >maximum number of connections. Our savior has been PoolMan > >http://www.codestudio.com, which we are using with jrun, and has stood up to > >medium to heavy traffic and load testing with no problems. > > > > > > [EMAIL PROTECTED] (512)-236-6244 > >--- > >I bet the main reason the police keep people away from a plane crash is they > >don't want anybody walking in and lying down in the crash stuff, then when > >somebody comes up act like they just woke up and go, "What was THAT?!" -- > >Deep Thoughts by Jack Handey > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [SMTP:[EMAIL PROTECTED]] > > > Sent: Wednesday, February 20, 2002 10:22 AM > > > To: [EMAIL PROTECTED] > > > Subject: JRun-Talk-List V1 #88 > > > > > > JRun-Talk-List Wed, 20 Feb 2002 Volume 1 : > > > Number 88 > > > > > > In this issue: > > > > > > Caching connection > > > RE: Caching connection > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Date: Wed, 20 Feb 2002 10:56:28 -0500 > > > From: [EMAIL PROTECTED] > > > Subject: Caching connection > > > Message-ID: <[EMAIL PROTECTED]> > > > > > > Our office is new in implementing J2E technology. We are set up with JRun > > > and ms > > > sql server. The db admin was horrifed when he opened the sql server log > > > and saw > > > all the connections by one of my applications. > > > > > > > > > Basically, the site queries the db almost at every page, to collect, > > > display the > > > different info. So everytime the user browses a page, data is being > pulled > > > from > > > sql. > > > > > > > > > Am I doing anything wrong? I thought that everytime I connect, I should > > > close > > > the connection. > > > > > > > > > I posted this q to javaranch, and one person replied that i should store > > > in app > > > level, and another one that JDBC2 Datasource would do that for me. > > > > > > > > > I'm embarrassed to admit but am clueless of what they mean. Can someone > > > please > > > explain? > > > > > > > > > Thanks! > > > > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
