Sessions Do Not Timeout in Oracle ADF Based Application After Setting Session Timeout to 120 Minutes in JDeveloper

(Doc ID 987026.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle JDeveloper - Version: to
Information in this document applies to any platform.


Oracle ADF based application can not use 120 min session timeout, as it appears that some javascript pings server for .cur files at roughly 90 minute interval causing session to stay alive.

### Steps to Reproduce ###
The Application was developed using Oracle ADF and test was repeated with 5, 35, 60 and 120 minute as session timeout in web.xml.

  1. Set timeout in web.xml and deploy.
  2. Launch application. Use a separate desktop to launch and lock it so that there is no way application is accessed.
  3. Optional for Unix system, tail access log of web server. Use grep with your id if this is a shared webserver.
  4. Wait 5 minutes longer than timeout.
  5. Try the application again.
  6. For 5, 35, 60 minute session timeout, there will be nothing in access log, and you will get session timeout.
  7. For 120 minute session timeout, you will see that even if you did not access any page, application session will not timeout.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms