Re: Why doesn't Oracle kill dead connections?

2002-01-20 Thread Mogens Nørgaard
Agreed. [EMAIL PROTECTED] wrote: I believe in your case no since the browser is not connected to the database, but the web server is and is alive. The real issue is does the web server know that the client closed his/her browser and terminate the session. I doubt it. Dick Goulet

RE: Why doesn't Oracle kill dead connections?

2002-01-16 Thread Karniotis, Stephen
Much of this is controlled through Oracles 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 didnt work well) that can assist in dead connection

Re: Why doesn't Oracle kill dead connections?

2002-01-16 Thread Mogens Nørgaard
DCD was invented and implemented for 7.1 of Oracle because of the strange and wonderful handling of timeout stuff in Unix. Typically, it can take between 8 and 80 hours for Unix to discover that a session should be killed since it no longer has a connection to the Oracle database. The problem

Re: Why doesn't Oracle kill dead connections?

2002-01-16 Thread Sona
But in my case if DCD is set up and the browser is closed will the web server know that the connection has been closed and will it tell Oracle to kill the session? TIA - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Wednesday, January 16, 2002