From dgoulet@vicr.com Wed, 16 Jan 2002 07:50:06 -0800 From: dgoulet@vicr.com Date: Wed, 16 Jan 2002 07:50:06 -0800 Subject: Re:RE: Why doesn't Oracle kill dead connections? Message-ID: MIME-Version: 1.0 Content-Type: text/plain Question 1 is how long does the report take to run? If you have DCD set up with 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@Compuware.com Web: 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

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:         &n bsp;   Stephen.Karniotis@Compuware.com

Web:         &n bsp;    www.compuware.com

 

 

-----Original Message-----
From: Sona [mailto:sona_us@hotmail.com]
Sent: Tuesday, January 15, 2002 7:20 PM
To: Multiple recipients of list ORACLE-L
Subject: Why doesn't Oracle kill dead connections?

 

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

-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: dgoulet@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@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).