How to kill the session after the user exit the ADF application

Question

Dear all
I have a problem
The problem is the session still exist after the user close the application and the browser. I want to kill all sessions that is not active.
This is my test scenario:
1- I open IE and run my ADF application that is deployed on weblogic. http://192.168.100.17:7001/myapp/faces/login
2- At the same time I issue this SQL command to view the sessions for user 'ADFUSER' - the "ADFUSER" is the schema user.
SELECT USERNAME,STATUS FROM v$session
WHERE USERNAME = 'ADFUSER';QUERY RESULT IS
USERNAME                       MODULE                                           STATUS
ADFUSER                         JDBC Thin Client                                 INACTIVE3- Now the user close the browser
4- Run the SQL again and I notice that the session still exist
SELECT USERNAME,STATUS FROM v$session
WHERE USERNAME = 'ADFUSER'RESULT:
USERNAME                       MODULE                                           STATUS
ADFUSER                        JDBC Thin Client                                 INACTIVE5- now the user open the URL again http://192.168.100.17:7001/myapp/faces/login
6-Run the SQL again , and I notice that the old session still exists and a new session created too.
SELECT USERNAME,STATUS FROM v$session
WHERE USERNAME = 'ADFUSER'RESULT:
USERNAME                       MODULE                                           STATUS
ADFUSER                        JDBC Thin Client                                 INACTIVE
ADFUSER                        JDBC Thin Client                                 INACTIVE
2 rows selected.and every time I login to the application , a new session is open and the old session still exist
I do not know why this happens
I want to kill old session when the user close the application.
These sessions are cleared only when i restart the weblogic domain.
here is some information about my development environment:
Jdeveloper 11.1.2.3
WebLogic Server Version: 10.3.5.0
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
thanks in advance

Answer 1

Hi,
for performance reasons you should not use dedicated user connections to the database. Instead you use JDBC data sources (default in JDeveloper for ADF BC) that you can configure the database connection pooling for. This means that your v$session will always show a set of active session, which however are shared among users. Assuming you use ADF BC, this is what happens
- A user requests a data bound page
- The ADF BC checks out an AM and connects to the database using one of the database connections in the pool
... user work here ...
- user exits application
- ADF BC returns AM to pool and passivates pending user state (if application is left with dirty transaction)
- Database connection is available in pool as soon as AM released
This also happens between requests. Long story cut short: v$session doesn't give you a true picture
Frank