Hi Vimal: Thank you for your reply. We are using a patch already - Weblogic App Server 5.1 Service Pack 10 (SP10). I would imagine that the fix is implemented in this patch, right?
Regards, Abhi --- "Sharma,Vimal" <[EMAIL PROTECTED]> wrote: > Patch :CR063414_610sp2.jar > To install it, you just have to copy the file > CR063414_610sp2.jar in your lib directory and add > his path to the beginning of the CLASSPATH of your > startWeblogic.sh > > -----Original Message----- > From: WHITESIDE, CHIP > [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 11:05 AM > To: Sharma,Vimal > Cc: '[EMAIL PROTECTED]' > Subject: RE: [jdjlist] RE: Closing Connections!!?? > > > Do you happen to know the CR# for the patch? > > > > > -----Original Message----- > > From: Sharma,Vimal > [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, June 06, 2002 11:00 AM > > To: JDJList > > Subject: [jdjlist] RE: Closing Connections!!?? > > > > > > Hi Abhilash, > > > > We recently face this problem and found bug in > Weblogic App > > server. It doesn't close the connections in case > of > > "Interrupted Requests" from browser. There is a > patch > > available with BEA. > > > > > > > > > > > > -----Original Message----- > > From: Abhilash Nair [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, June 06, 2002 10:51 AM > > To: JDJList > > Subject: [jdjlist] Closing Connections!!?? > > > > > > Hi All: > > > > We are using Oracle Thin Type 4 Driver with > Weblogic > > App Server version 5.1 for our JDBC Connections > and > > use Prepared Statements. We also have specified > the > > maximum connections to be 100 in the weblogic > > properties and in our DAO's we close the > > PreparedStatement, ResultSet and Connection in the > > finally block. But there are STILL instances where > the > > connections are not being closed even when the > > following code is executed: > > > > try{ > > //create connection,etc. > > }catch(SQLException sqlExc){ > > //handle error > > }finally{ > > try { > > if(rs != null){ > > rs.close(); > > } > > if(prepStmt != null){ > > prepStmt.close(); > > } > > if(con != null){ > > con.close(); > > } > > } catch(SQLException e) {;} > > } > > > > Problem faced: Exceeding the maximum number of > > connections due to inactive open connections. Has > > anyone faced this problem? > > > > I thought that the finally block is executed no > matter > > what and is the best place to close connections to > > ensure a proper clean - up! Can anyone please > suggest > > what am I doing wrong here? > > > > Thanks in advance. > > Abhi > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! - Official partner of 2002 FIFA World Cup > > http://fifaworldcup.yahoo.com > > > > To change your membership options, refer to: > > http://www.sys-con.com/java/list.cfm > > > > To change your membership options, refer to: > > http://www.sys-con.com/java/list.cfm > > > > To change your membership options, refer to: > http://www.sys-con.com/java/list.cfm ===== You can reach me on: Weekdays: (617)509-5312 Weekends and evenings: (781)321-2065 Pager: (781)553-8323 Thanks and Regards, Nair Abhilash R (Abhi) __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To change your membership options, refer to: http://www.sys-con.com/java/list.cfm
