I think the question is based on a slight misunderstanding...
> > Don't rely on the pool to autocollect your abandoned connections:
> > return [ your connections ] explicitly [ before they become
abandonded ].
[ clarifications ]
('them' did not refer to abandonded connections).
> -----Original Message-----
> From: Hofmann, Benjamin [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 09, 2004 10:36 AM
> To: 'Tomcat Users List'
> Subject: RE: JNDI connection pool leaks in Tomcat 5
>
>
> That is a good question. In the past, the datasource classes
> overrode the
> close() method to mean "put it back" instead of an actual
> close. I'm not sure in this case because the close() method
> in the org.apache.commons.dbcp.BasicDataSource means "Close
> and release all connections that are currently stored in the
> connection pool associated with our data source."
>
> Ben
>
> -----Original Message-----
> From: Paul [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 09, 2004 9:55 AM
> To: Tomcat Users List
> Subject: Re: JNDI connection pool leaks in Tomcat 5
>
> what is the code to return abandoned connections explicitly?
>
> ----- Original Message -----
> From: "Shapira, Yoav" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>
> Sent: Tuesday, March 09, 2004 10:23 AM
> Subject: RE: JNDI connection pool leaks in Tomcat 5
>
>
> >
> > Hi,
> >
> > >I have been setting up the new Tomcat 5 and it looks like the
> > documentation
> > >has not been updated. I see that it has a high priority though. I
> > also
> > >noticed that the removeAbandoned, removeAbandonedTimeout, and
> > logAbandoned
> > >get/set methods are deprecated in Tomcat 5. They were used to
> > >control connection pool leaks in Tomcat 4.
> > >
> > >Does this mean that the leak problem has been fixed or is there
> > >another
> > way
> > >to control it?
> >
> > When you say you see or notice stuff, it helps if you quote
> the source
> > URL. The abandoned handlers that you refer to were
> deprecated by the
> > DBCP team, and tomcat reflects that change as tomcat uses
> the latest
> > stable DBCP version. If you have an issue with their
> design decisions
> > (and this particular one was discussed heavily), contact them: it's
> > jakarta's commons-dev mailing list that you'd want.
> >
> > Don't rely on the pool to autocollect your abandoned connections:
> > return them explicitly.
> >
> > Yoav Shapira
> >
> >
> >
> > This e-mail, including any attachments, is a confidential business
> communication, and may contain information that is
> confidential, proprietary and/or privileged. This e-mail is
> intended only for the individual(s) to whom it is addressed,
> and may not be saved, copied, printed, disclosed or used by
> anyone else. If you are not the(an) intended recipient,
> please immediately delete this e-mail from your computer
> system and notify the sender. Thank you.
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
