Yoav is correct, you should be using the newer driver and not the older one. good thing I asked which version the driver is.
that's a really old bug in the old driver. I remember reporting the bug back in 99 and the support rep said something like, "yeah, lots of people have been reporting the bug." peter On Tue, 28 Sep 2004 14:16:43 -0400, Shapira, Yoav <[EMAIL PROTECTED]> wrote: > > Hi, > You're wrong. You can and should use classes12.zip (renamed to > classes12.jar) with Oracle 8i. You can even use the modern ojdbc14.jar > drivers. > > Yoav Shapira > Millennium Research Informatics > > > > > >-----Original Message----- > >From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, September 28, 2004 2:09 PM > >To: Tomcat Users List; Peter Lin > >Subject: RE: Tomcat 4.1 Connection Pooling... > > > >I am using Oracle 8i, and Oracle drivers i use is Oracle111.jar, and > use > >DBCp for connection Pooling with Tomcat4.1, > >i thought classes112 is for 9i...correct me if i am wrong... > > > >-----Original Message----- > >From: Peter Lin [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, September 28, 2004 2:01 PM > >To: Tomcat Users List > >Subject: Re: Tomcat 4.1 Connection Pooling... > > > > > >I thought Oracle fixed that bug in their connectionPooling driver back > >in 2001. Am I missing something? Are you using some other driver to > >create a pool of jdbc connections to Oracle? sorry for the question if > >it's already been answered in earlier messages. > > > >I've used classes112.zip jdbc driver from oracle without any problems > >with connection pooling. If you're using classes111.zip driver from > >oracle, you should update your driver to the latest. > > > >just in case no one else mentioned it. > > > >peter > > > > > >On Tue, 28 Sep 2004 13:55:18 -0400, Shapira, Yoav > <[EMAIL PROTECTED]> > >wrote: > >> > >> Hi, > >> Hmm ;) There's a good reason there's no close method on > >> javax.sql.DataSource. There's also a good reason the J2EE spec calls > >> for the container, not the user, to manage the lifecycle of JNDI > >> resources such as DataSources. IF you go with this > >> ServletContextListener approach to take over lifecycle management of > a > >> server-provided JNDI resource, you'll be in a murky space at best. > >> > >> Yoav Shapira > >> Millennium Research Informatics > >> > >> >-----Original Message----- > >> >From: Phillip Qin [mailto:[EMAIL PROTECTED] > >> >Sent: Tuesday, September 28, 2004 1:27 PM > >> >To: 'Tomcat Users List' > >> >Subject: RE: Tomcat 4.1 Connection Pooling... > >> > > >> >For connecion pooling, when you close the connection, you don't > >> actually > >> >close the physical link. After several shutdown/sartup of your > >> application, > >> >open connection accumulates and exceeds Oracle's 200 thus you > receive > >> that > >> >SQLException. > >> > > >> >To solve your problem, I would implement a ServletContextListener to > >> >initialize connection pool when my context is in the initialization > >> (public > >> >method contextInitialized) and close data source when my context is > >> >destroyed (public method contextDestroyed). > >> > > >> >If you have defined loadonstartup servlet in your web.xml, in the > >> destroy > >> >method, explicitly close your data source. > >> > > >> > > > >--------------------------------------------------------------------- > >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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
