a time-out of 1 second your network is going to take a heck of a hit just from
probe packets. The most common setting I've run into is 15 to 30 minutes so
that does not help. Setting up a profile for the Internet user that allocates a
max cpu can likewise be nasty in that the time allocation may not be large
enough for the report to run. This can get especially frustrating as the amount
of data that the report must process grows. The last point is that I do not
believe DCD works with sessions that are ACTIVE since the client side (yes the
OAS server is a client) is waiting for the database and not responding to
anything else. I believe it only works with INACTIVE sessions which is not your
problem. The other point is that the WEB is a stateless world where even the
web server may not be cognizant of the client closing his/her browser. Do you
have the same problem if the client hits the STOP button?
Dick Goulet
____________________Reply Separator____________________
Author: "Karniotis; Stephen"
Date: 1/16/2002 6:15 AM
Much of this is controlled through Oracle's SQL*Net product. It needs to be
configured. It also depends on what version of the database you are using.
Oracle8.0/8i and beyond have mechanisms called profiles (oracle7 had them as
well but didn't work well) that can assist in dead connection detection.
The problem with Web-based dead connection is that if the application server
retains the connection, the stuff will work. However, if the application
server has started the SQL/PL/SQL process and then goes off to do other
work, and return back, the dead connection stuff may disconnect you by
accident.
Guess it is trial and error.
Thank You
Stephen P. Karniotis
Technical Alliance Manager
Compuware Corporation
Direct: (248) 865-4350
Mobile: (248) 408-2918
Email:
Stephen.Karniotis_at_Compuware.com
Web: <http://www.compuware.com/> www.compuware.com
-----Original Message-----
Sent: Tuesday, January 15, 2002 7:20 PM
To: Multiple recipients of list ORACLE-L
Hi
I have a Reporting appliaction. The reports are run from the browser . The
reports are basically Pl/SQL packages .the request is made from the browser
and then communicated to the database thru OAS .(oracle application server)
which acts as web server.
The problem is when a user executes a report (i.e. hits the RUN button) and
then closes the broser before the execution of the report is
completed.Oracle still contimues running the query in the database. The
session still remains ACTIVE in the database even though the client has
closed the connection (i.e. the user has closed the browser).
Is there any way to force Oracle to kill the session when the user closes
the browser?
TIA
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
" rel="nofollow">http://www.w3.org/TR/REC-html40">
<!--
/* Font Definitions */
@font-face
<pre>
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;
mso-font-charset:0;
mso-generic-font-family:script;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
@font-face
{font-family:"Monotype Corsiva";
panose-1:3 1 1 1 1 2 1 1 1 1;
mso-font-charset:0;
mso-generic-font-family:script;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:553679495 -2147483648 8 0 66047 0;}
@font-face
{font-family:Haettenschweiler;
panose-1:2 11 7 6 4 9 2 6 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:647 0 0 0 159 0;}
</pre>
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
<pre>
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
span.EmailStyle15
{mso-style-type:personal-reply;
mso-ansi-font-size:11.0pt;
mso-ascii-font-family:"Comic Sans MS";
mso-hansi-font-family:"Comic Sans MS";
mso-bidi-font-family:Arial;
color:navy;
font-weight:normal;
font-style:normal;}
p.BodyCopy, li.BodyCopy, div.BodyCopy
{mso-style-name:"Body Copy";
mso-style-update:auto;
margin-top:0in;
margin-right:0in;
margin-bottom:7.0pt;
margin-left:0in;
line-height:14.0pt;
mso-line-height-rule:exactly;
mso-pagination:widow-orphan;
font-size:11.0pt;
mso-bidi-font-size:10.0pt;
font-family:Garamond;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
mso-ansi-font-size:10.0pt;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:black;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
</pre>
-->
Much of this is controlled through Oracle’s
SQL*Net product. It needs to be
configured. It also depends on
what version of the database you are using. Oracle8.0/8i and beyond have mechanisms called profiles
(oracle7 had them as well but didn’t work well) that can assist in dead
connection
detection.
The problem with Web-based dead connection is that
if the application server retains the connection, the stuff will work. However, if the application server has
started the SQL/PL/SQL process and then goes off to do other work, and return
back, the dead connection stuff may disconnect you by
accident.
Guess it is trial and
error.
style='mso-bidi-font-style:
normal'>Thank
You
Stephen P.
Karniotis
Technical
Alliance Manager
Compuware
Corporation
Direct:
(248)
865-4350
Mobile:
(248)
408-2918
Email: &n
bsp; Stephen.Karniotis_at_Compuware.com
Web: &n
bsp; www.compuware.com" rel="nofollow">http://www.compuware.com/">www.compuware.com
-----Original
Message-----
From: Sona
Sent: Tuesday, January 15, 2002
7:20 PM
To: Multiple recipients of list
ORACLE-L
Subject: Why doesn't Oracle kill
dead connections?
style='font-size:10.0pt;font-family:Arial;color:black'>Hi
I have
a Reporting appliaction. The reports are run from the browser . The reports are
basically Pl/SQL packages .the request is made from the browser and then
communicated to the database thru OAS .(oracle application server) which
acts as web server.
The
problem is when a user executes a report (i.e. hits the RUN button) and then
closes the broser before the execution of the report is completed.Oracle still
contimues running the query in the database. The session still remains ACTIVE
in the database even though the client has closed the connection (i.e. the user
has closed the browser).
Is
there any way to force Oracle to kill the session when the user closes the
browser?
style='font-size:12.0pt;color:black'>
style='font-size:10.0pt;font-family:Arial;color:black'>TIA
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: dgoulet_at_vicr.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).