idle_time

I know how to set up resource limits via profile to change the time for the idle_limit value. What I see happen is that if the session is idle for more then the set resource limit, then the session is flagged as idle. But I still see the session in the v$session view. As soon as the idled session trys to do something again, it gets the diconnected message and the session disappears for the v$session view.

My question is that since the server has recognized the session as having been idle too long, shouldn't the session be removed then instead of an the next attemp to access the server?

Why time out sessions if they are not removed at time out detection?

Am I missing something here?

TIA

--
TEXAS NATURAL RESOURCE CONSERVATION COMMISSION
CHARLIE LANCASTER Mail Code 197
P O BOX 13087 AUSTIN, TX 78711-3087
Phone:512-239-0795 FAX:512-239-0888 e-mail:clancast_at_tnrcc.state.tx.us