Alex Turner wrote:
Somehow I doubt the JSTL authors were so short sighted as not to
release database connections properly. I'm sure they had production
usage in mind when it was written, I'm just wondering how.
Actually, they seemed to mostly have rapid prototyping in mind with the
JSTL SQ
> From: Alex Turner [mailto:[EMAIL PROTECTED]
> Subject: Re: Connection Pool Woes
>
> How does registering my pooling datasource with a naming directory
> help connection management?
It's doesn't - the JNDI suggestion is a red herring. Even with
connection pooling, you
ry 23, 2006 11:54 AM
> To: Tomcat Users List
> Subject: Re: Connection Pool Woes
>
>
> How does registering my pooling datasource with a naming
> directory help connection management? (Honest question - I
> really don't know)
>
> Alex.
>
> On 1/23/06, Asad Hab
How does registering my pooling datasource with a naming directory
help connection management? (Honest question - I really don't know)
Alex.
On 1/23/06, Asad Habib <[EMAIL PROTECTED]> wrote:
> You should use JNDI with your connection pool to ensure that connections
> are being managed appropriat
I'll just point out here that you actualy haven't pointed out any issue.
I asked a question as to how, and you repsonded that it was an issue
without ever explaing how, or if there even is a problem.
Somehow I doubt the JSTL authors were so short sighted as not to
release database connections pro
You should use JNDI with your connection pool to ensure that connections
are being managed appropriately.
- Asad
On Mon, 23 Jan 2006, Chris McCormack wrote:
Its poor practise to have a sql: jstl tag in production ready code.
How do you deal with this when using pure JSTL sql calls using a
Its poor practise to have a sql: jstl tag in production ready code.
> How do you deal with this when using pure JSTL sql calls using a
> connection? How does JSTL sql library release the connection at the
> end of a page to ensure that connections don't get leaked?
For reasons exactly like th
nection, but some pages are pure JSP.
>
> Alex.
>
> On 1/20/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> >
> >
> > > -Original Message-
> > > From: Alex Turner [mailto:[EMAIL PROTECTED]
> > > Subject: Re: Connection Pool Woes
&
ction, but some pages are pure JSP.
Alex.
On 1/20/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Alex Turner [mailto:[EMAIL PROTECTED]
> > Subject: Re: Connection Pool Woes
> >
> > It looks like the connection
> -Original Message-
> From: Alex Turner [mailto:[EMAIL PROTECTED]
> Subject: Re: Connection Pool Woes
>
> It looks like the connection object was not being garbage collected
> promptly (imagine that), and because it wasn't explicitly closed, it
> was just
It looks like the connection object was not being garbage collected
promptly (imagine that), and because it wasn't explicitly closed, it
was just hanging open until garbage collection happened (I'm more used
to python's garbage collector that is a bit more prompt).
Alex
On 1/20/06, Duan, Nick <[E
The only way to close db connections is to do within your servlet/jsp
application, i.e. java.sql.Connection.close(). But remember, the sql
connections in the web apps are not the physical connections. The
physical connections are maintained by the db pool and they will remain
open after the conne
> From: Alex Turner [mailto:[EMAIL PROTECTED]
> Subject: Connection Pool Woes
>
> I have a server that is set to maxThreads="5", maxSpareThreads="5",
> and when I use a Simply Data Source, that does not pooling, if I hit
> the page a lot, I get over 30 connections opened, with database
> connecti
13 matches
Mail list logo
