+When a request is sent to the server, a session timeout value is written to the page and the session timeout warning interval is defined by the context parameter oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT. The user is given the opportunity to extend the session in a warning dialog, and a notification is sent when the session has expired and the page is refreshed. Depending on the application security configuration, the user may be redirected to the log in page when the session expires.+
+Use the oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT context parameter to set the number of seconds prior to the session time out when a warning dialog is displayed. If the value of WARNING_BEFORE_TIMEOUT is less than 120 seconds, if client state saving is used for the page, or if the session has been invalidated, the feature is disabled. The session time-out value it taken directly from the session.+
+Example A-3 shows configuration of the warning dialog to display at 120 seconds before the time-out of the session.+
+Example A-3 Configuration of Session Time-out Warning+
+The default value of this parameter is 120 seconds. To prevent notification of the user too frequently when the session time-out is set too short, the actual value of WARNING_BEFORE_TIMEOUT is determined dynamically, where the session time-out must be more than 2 minutes or the feature is disabled."+
As there is no parameter to configure the URL for the link, I suggest to disable the feature:
Use the oracle.adf.view.rich.sessionHandling.WARNING_BEFORE_TIMEOUT context parameter to set the number of seconds prior to the session time out when a warning dialog is displayed. If the value of WARNING_BEFORE_TIMEOUT is less than 120 seconds, if client state saving is used for the page, or if the session has been invalidated, the feature is disabled. The session time-out value it taken directly from the session
Before I can file an ER, I need to know
1. Which Version of JDeveloper
2. Why is the server you run configured with local host IP address. I am not sure the proxy server understands how to map this at all. Did you try a server name or real IP address
Edited by: Frank Nimphius on May 31, 2012 10:19 AM
1) We use this version JDEVADF_184.108.40.206.0_GENERIC_110531.1615.6017 for development.
2) What I posted is my testing program in my PC, for our testing environment the hostname is the real IP like 192.168.1.101.
The real script is the following in our production:
AdfPage.PAGE.__recordSessionTimeout(1800000, 60000, "http://192.168.1.101:80/App/faces/Login.jspx");
I also checked the Oracle ADFDemo.
In the demo application, the script is the following:
AdfPage.PAGE.__recordSessionTimeout(2100000, 120000, "/ADFDemo-ADFDemo1112-context-root/faces/accessibility.jspx")
This is what I want.
Inside the script object AdfPage, this function __recordSessionTimeout will use window.location.replace to handle the newSessionURL.
If the intranet IP address is the hostname for the newSessionURL, this action of window.location.replace will fail.
I don't for sure what kind of context parameters will affect this.
apparently this has been filed as bugs 13922784 and 14033097 and is scheduled to be fixed in 12c. You can check if the hostname of yours appears in the JavaEE path (e.g. http://mycomp.com:7001/mycomp/...) if this is the case, the fix is to change the Java EE path
The hostname is in the path, and it's the intranet ip of the server.
We have some clients who access this application through intranet, for these users there is no problem for accessing the application if the JavaEE path including the hostname because the client side and server side are in the same network.
Also we have some clients who access this application through internet by apache proxy which is in our DMZ, for these users if the intranet ip is in the JavaEE path there should be the problem.