Howdy, You don't need to synchronize pool access for DBCP at the calling application level (which is your level). You also don't need to keep a reference to the initial or lookup context, just the datasource. Make sure to clean and null out the datasource reference in your servlet's destroy() method.
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Marco Tedone [mailto:[EMAIL PROTECTED] >Sent: Sunday, September 07, 2003 4:13 AM >To: Tomcat Users List >Subject: Re: JNDI DataSource - need to synchronize? > >Well, to be sure, put your variables inside the methods. This way, your >data >will be safe. One idea would be to create objects when you need them, and >to >close them when you've finished. > >Marco >----- Original Message ----- >From: "john-paul delaney" <[EMAIL PROTECTED]> >To: "Tomcat Users List" <[EMAIL PROTECTED]> >Sent: Sunday, September 07, 2003 12:18 PM >Subject: JNDI DataSource - need to synchronize? > > >> Hello List... >> >> Some coding help please. Following earlier advice on this list and the >TC >datasource how-to, I've now got a working test servlet. Basically I >declare >the Context(s) and DataSource as instance variables, and initialize them in >init: >> >> ======================================================== >> Context initContext = null; >> Context envContext = null; >> DataSource ds = null; >> >> public void init() throws ServletException { >> >> try { >> initContext = new InitialContext(); >> >> envContext = (Context) initContext.lookup( >> "java:comp/env"); >> ds = (DataSource) envContext.lookup( >> "jdbc/jpdb"); >> } catch (NamingException e) { >> >> throw new ServletException( >> "Couldn't setup JNDI Context/DataSource", e); >> >> } >> } >> ========================================================== >> >> If this is the correct approach, should I be synchronizing the >Context(s)/DataSource in the doGet method? If another http request thread >closes it's own connection, will it affect the Context or DataSource object >of this request? >> >> Thanks for any clarification, >> /j-p. >> >> >> --------------------------------------------------------------------- >> 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] 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]
