 | 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 Richard Yee
Back
ShriKant,
I'd suggest yanking the code that gets the db connection in the servlet
init() and change the code so that the connection is obtained in the doPost
or doGet method. Also close the connection in a finally block in the same
method.
The current code you have should result in a stale and closed connection
on the second request.
-Richard
At 03:03 PM 10/11/2003 -0700, you wrote:
>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!?
><http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext
%2Csec%3Amail>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)
====================================================================
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)
<html>
ShriKant,<br>
I'd suggest yanking the code that gets the db connection in the servlet
init() and change the code so that the connection is obtained in the
doPost or doGet method. Also close the connection in a finally
block in the same method.<br>
The current code you have should result in a stale and closed
connection on the second request.<br><br>
-Richard<br><br>
At 03:03 PM 10/11/2003 -0700, you wrote:<br><br>
<blockquote type=cite class=cite cite>Hi,<br>
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.<br>
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:<br>
try{<br>
connection = getDBConnection();<br>
session.setAttribute("conn", connection);<br>
}catch(Exception e){<br>
doSomething()<br>
}finally(){<br>
closeConnection();<br>
}<br>
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.<br>
Please suggest!<br>
-ShriKant<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br><br>
<dl>
<dd> <br><br>
</dl><br>
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:
<a href="http://www.corej2eepatterns.com/" eudora="autourl">http://www
.corej2eepatterns.com</a>
J2EE BluePrints: <a href="http://java.sun.com/blueprints/corej2eepatterns"
eudora="autourl">http://java.sun.com/blueprints/corej2eepatterns</a> List
Archive: <a href="http://archives.java.sun.com/archives/j2eepatterns-interest
.html" eudora="autourl">http://archives.java.sun.com/archives/j2eepatterns
-interest.html</a> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST"
; to listserv@(protected) </blockquote></html>
====================================================================
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)
|
|
|
