Not a direct answer to your problems, Vic, but we decided to use our own
pooling mechanism for a number of reasons:
- portability across application servers (a requirement for our business)
- easier to tune (set # of initial connection and max # of connections at
runtime)
- easier to customize
- ability to use the same pooling mechanism from a web-app or a standalone
app.
We adapted the nice threaded pool from Marty Hall's "Core Servlets & JSP"
(www.coreservlets.com), enhancing logging and adding the ability to read the
init parameters from a file. We also wrote a static wrapper class which is
especially useful in a web-app context.
One advantage of this pool is that it returns a real Connection object, not
a proxy or subclass. On the other hand, your client code needs to call the
pool's free() method rather than Connection.close() when it's done. So, you
can't just drop pooling into an exisint app without modifying your jdbc
code.
Our pooling class needs some enhancements, too, but they won't be hard to
implement.
Joe Niski | Senior Software Engineer/Internet Architect
503.548.2176
CYBERSIGHT
strategy . marketing . design . technology
los angeles . portland . san francisco . toronto
> -----Original Message-----
> From: Victor Marinelli [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 6:03 AM
> To: JRun-Talk
> Subject: Re: database connections are not closing
>
>
> In addition to the connection pool problems I am seeing, is
> there a way to
> limit the size of the pool in JRun? Another words, set a
> limit to the amount
> of connections the pool can open to like 10 or so? ( I
> apologize if this
> question has already been answered).
>
> Vic
>
>
>
> ----- Original Message -----
> From: "Jay Walters" <[EMAIL PROTECTED]>
> To: "JRun-Talk" <[EMAIL PROTECTED]>
> Sent: Thursday, May 03, 2001 9:09 PM
> Subject: RE: database connections are not closing
>
>
> > The connections are supposed to stay open, that is the purpose of
> connection
> > pooling. To open the connections once and keep them open.
> When you close
> > the connections within your application they are just put
> back in the
> pool.
> >
> > Cheers
> > Jay
> >
> > -----Original Message-----
> > From: Victor Marinelli
> > To: JRun-Talk
> > Sent: 5/3/01 2:43 PM
> > Subject: database connections are not closing
> >
> > Hello,
> >
> >
> > I am using JRun 3.0 and Apache 1.3.14 on Solaris. I am
> using Informix
> > IDS
> > 2000 as the database. I noticed that everytime I access my web
> > application
> > and do a query, database connections remain open! They don't seem to
> > ever
> > close. I had a total of 49 connections open. I enabled connection
> > pooling
> > through JMC and I checked my code to make sure I was closing the
> > dbConnection. I don't know what to try at this point and this is a
> > serious
> > problem. Can someone please help!!
> >
> >
> > Thanks,
> > Vic
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
