Re: help with disconnecting users after idle time expires *in WEBDB*?

From: Frank <frankbo_at_interaccess.nl>
Date: Wed, 6 Sep 2000 10:07:30 +0200
Message-ID: <8p4u0e$oqa$1_at_porthos.nl.uu.net>

I am not quite sure what your problem is; the fact that a web browser stays open with what appears to be a database connections?
Yes - appears to be!

What happens with a typical web application is this:

1) you type in the address and send your browser window.
2) your screen wanders off into the big IP world
3) you web server picks it up and interprets it
4) in your case, a cgi or pl/sql agent is activated. (I only know pl/sql

cartridge, so I"ll continue with that)
5) in the pl/sql cartrigde, a useris/passwd/connect string is either specified, or asked for
6) the connection is made (ws to rdbms), procedure called and executed, and html formatted string

   returned.

7) the connection is released (ws to rdbms)
8) your ws sends it back to the big IP world
9) your browser picks it up (if still active)

so, point to note here: between 1 and 3, there's no "connection" between your browser and the webserver.
Same is true for 8/9.
Also, 6 makes the connection, 7 releases it.

This is known as non-persitant connections, and these are common on the www (and one of the biggest
problems - there's no garantuee the data will endup in the same place it was requested from...

hth,

--
Frank
Geoff Glave <geoffg_at_istar.ca> schreef in berichtnieuws
39b5a455$1_at_rsl2.rslnet.net...


> SUBJECT: Disconnecting users after idle time expires *in WEBDB*

>

> Hello All,


>

> We would like to have users be disconnected from our Oracle database after

 1


> hour of inactivity, even if they connect through webdb.


>

> The users are all set up with a profile that has an idle time of 1 hour,

 and


> I have also changed the resource_limit = true in the initxxx.ora file.


 (And


> I did bounce the database).  This works great if the users connect via SQL


> Worksheet or some other application.  However, if they connect via WebDB

 (or


> through webdb via OAS) they can stay connected as long as the browser is


> open.

>

> Does anybody know of any work-arounds for this problem?

>

> Thanks in advance - Email replies appreciated (just remove the "NOSPAM")

>

> Jacquie Armstrong

> Soft Tracks

> Vancouver, Canada

> jacquieNOSPAM_at_softtracks.com

>

>

>

Received on Wed Sep 06 2000 - 10:07:30 CEST