 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Offbeat:DB connection Problem | Offbeat:DB connection Problem 2003-10-11 - By ShriKant Vashishtha
Back
Hi,
I am sorry as I know this problem is not related to this list, but if
anybody could throw some light on this, I will be thankful.
I got a maintenance code in which somebody is getting the DB connection in
the servlet and for the purpose of passing it throughout the request,
connection instance was storing in session.
So the scenario is something like this:
try{
connection = getDBConnection();
session.setAttribute("conn", connection);
}catch(Exception e){
doSomething()
}finally(){
closeConnection();
}
I know that it is totally ridiculous to put the connection in the session.
Even then, the question is: when I close the connection in finally block,
what happens to the connetion instance which is lying in the session. In my
view either it is stale reference or it is still open. If it is open then
it is a resource leak.
Please suggest!
-ShriKant
-- ---- ---- ---- ---- ---- -----
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<DIV><BR>Hi,</DIV>
<DIV>I am sorry as I know this problem is not related to this list, but if<BR
>anybody could throw some light on this, I will be thankful.</DIV>
<DIV>I got a maintenance code in which somebody is getting the DB connection in
<BR>the servlet and for the purpose of passing it throughout the request,<BR
>connection instance was storing in session.<BR>So the scenario is something
like this:</DIV>
<DIV>try{<BR>connection = getDBConnection();<BR>session.setAttribute("conn",
connection);<BR>}catch(Exception e){<BR>doSomething()<BR>}finally(){<BR
>closeConnection();<BR>}</DIV>
<DIV>I know that it is totally ridiculous to put the connection in the session.
<BR>Even then, the question is: when I close the connection in finally block,<BR
>what happens to the connetion instance which is lying in the session. In my<BR
>view either it is stale reference or it is still open. If it is open then<BR>it
is a resource leak.</DIV>
<DIV>Please suggest!<BR>-ShriKant</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR><BR>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER
-LEFT: #1010ff 2px solid"> </BLOCKQUOTE></DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk
%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
