Session Timeouts for Apps deployed on separate domains

Hi,
Jdeveloper : Studio Edition Version 11.1.1.2.0 , Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
Platform: Linux, Windows
I am observing something strange with session timeouts when 2 apps are deployed to 2 separate WLS instances.
Here is what I had done :
In JDeveloper, I create 2 Fusion Apps.
I create a simple JSPX page having a Tabbed Pane with 2 tabs in each of these apps.
I create a separate WLS domain with Admin server in it, using the weblogic's config tool.
I deploy one application in the embedded WLS instance and another application in the newly created domain's Admin server instance (for testing only) .
I access the jspx page in each of the app in 2 tabs from the same browser window.
When I click on the one application (i.e click on tabs in the tabbed pane) , the other application is timing out immediately. (definitely, the configured timeout limit of 6 minutes has not been reached)
Has anybody observed this ?
How can I circumvent this behavior ?
Thanks in advance
Sivan

The server set the session id, but its up to the browser to decide to use it or not.
If the browser sends a null session id, the server will generate a new one.
IE is well-known for sending null session id frequently to force renegotiation with the server.
Not sure what is the purpose of this, but it is annoying when doing stickyness.
Gilles.

Similar Messages

  • Hi I have two questions. I am using NAS 4.1 and was wondering is it possible to set a different session timeout for different users? How is the session timeout set? Thanks, YS

     

    <i>I am using NAS 4.1 and was wondering is it possible to set a different session timeout for different users?</i>
    Um, there is no such thing as NAS4.1.
    I'm assuming that you mean NAS4.0 (maybe NAS4.0sp1?). If so, then the session timeouts are specified in the session section of the NTV configuration files.
    AFAIK, you can specify session timeouts on a per user basis.

  • How to configure session timeout for SAP Netweaver Portal

    Hi,
    I would like to know the way to configure the session timeout for SAP Netweaver Portal.

    Hi Kim,
    the solution for your question  is in this thread.
    500 Connection timed out
    if it is helpful award me points.
    Regards,
    R.Suganya.

  • Iplanet 4.1 - How to set session timeout for a specific application

    Hi everyone,
    I have a Iplanet 4.1 old web instance running on Solaris 8. We are using this web instance to connect to few application instances running on Websphere 3.5. We have upgraded most of our web/app to higher version except this.
    One of the websphere applications need more session timeout. (Which I fuguredout not possible to do on Websphere).
    How do I achieve this on Iplanet 4.1.
    NOTE: I referred to Iplanet 6.x where we can achieve this by updating web-app.xml timeOut value per URI. I do not find web-app.xml under v4.1
    Thanks in advance,

    Sorry to say that we can't help here. WS4.1 is obsolete a long time ago.
    As you mentioned that you should use WS6.1SPx or WS7.0 for your production and get support.

  • How to create logs in to diff files for apps deploy on same OC4J instance?

    I am using OC4J 10.1.3.5 App server on Windows. I have deployed 2 web applications on the same instance of OC4J where I have defined the shared library. Both applications use Struts, Spring, iBatis, apache commons libraries which I have defined as a shared library. Part of the apache loggins library I had to add log4j jar as well. So indirectly log4j-12.16.jar is declared as a shared-lib as well.
    I have log4j.properties for both application pointing to different log file. But still when both applications are deployed and running, the logs are getting populated on only one file. During the deployment, I did check on webapp-classpath-first="true" setting to explicitly have log4j.properties of each individual application being load first. But nothing makes difference.
    Please help.
    Thanks
    Jasmin

    Jasmin,
    Dependent on where the log4j library is installed it will use either one or separate configuration files. Placed in WEB-INF/lib then the log4j logger is initialized separately for the applications using separate configuration files. This is not the case when the log4j library is placed under home/applib.
    regards,
    Bernhard Jongejan
    http://bernhardjongejan.spaces.live.com

  • Setting Session Timeout for HANA Cloud Portal

    Hi all,
    is there any way for setting the session timeout period on HANA cloud Portal?
    If not, what is the predefined session timeout?
    Thank you in advance.
    Silvia Grabmann

    Hi Silvia,
    Session timeout is 20 minutes and cannot be changed. In fact it is configured at the platform level.
    Regards,
    Ifat.

  • How to configure a session timeout for DynPro applications?

    Hello,
    1. Where can I configure the session timeout of the DynPro applications?
    2. Can I configure a session timeout per application and how do I do that?

    Hello Heidi,
    I am not familiar with this property:
    1. Where can I configure it?
    2. Does it apply to every application at the portal?
    3. What if I would like to configure just one application?
    By the way, I have noticed that the DynPro application has an expirationTime property. The documentation says this:
    Specifies the lifetime in seconds of a Web application on the server before the Web application is terminated by the server. The value of the DefaultExpirationTime parameter of the system configuration is used as the default value.
    My question is if someone tried to use this property?
    Message was edited by: Roy Cohen

  • Session timeouts for login page with in a html frame

    Hi, i have a login page which when the session times out gets redisplayed within the frame of the html page where the session timed out , i have tried setting the session timeouts to be less than the other application so that the login page will timeout before the documentum application but this does not make a difference.
    does any one know how i could get the login page to redisplay by itself, outside of the html frame. do i need to have some javascript to figure out if there is a frame then redraw the page etc...and how should i di this ? any working examples will be appreciated.

    You would certainly need some Javascript or use the meta-refresh tag to the session timeout time. If you set the meta-refresh tag in a frame to a time just a little bit bigger than the session timeout time and the set your security mechanisms to force the user to login in again when the session times out, the frame will refresh after the session has timed out and the application should forward the frame to the login page.
    <meta http-equiv="refresh" content="session-timeout-timeout+1">
    (timeout time is in seconds)

  • HELP!  Portal Stuck Checking for App Deployment

    We've got a portal application that appears to be constantly checking for appklication
    deployment, which slows things down significantly.
    We're not sure what we've done, But we get the following messages many times (about
    50-60) whenever we hit one of our portal pages:
    com.bea.wlw.runtime.core.dispatcher.AppManager - +ensureAppDeployment()
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - original URL= http://localhost:7001/ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - request URI= /ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - context path= /ctdportal
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - servlet path= /appmanager
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - path info= /ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - query string= null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - fReadRequest = false
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc request URI=/ctdportal/framework/skeletons/default/footer.jsp
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc context path=/ctdportal
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc servlet path=/framework/skeletons/default/footer.jsp
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc path info=null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc query string=null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - fixed request URL= http://localhost:7001/ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - service URL= http://localhost:7001/ctdportal/framework/skeletons/default/footer.jsp
    , virtual path= /ctdportal/framework/skeletons/default/footer.jsp , context path=
    /ctdportal , source path= framework/skeletons/default/footer.jsp , real path=
    C:\DevelCTD81\ctdportalApp\ctdportal\framework\skeletons\default\footer.jsp ,
    path encoded method name= null , SOAPAction= null , User-Agent= Mozilla/4.0 (compatible;
    MSIE 6.0; Windows NT 5.1; Q312461; GIL 2; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
    com.bea.wlw.runtime.core.dispatcher.LoadContext - application appDir=C:\DevelCTD81\ctdportalApp
    com.bea.wlw.runtime.core.dispatcher.LoadContext - Valid external build, suppressing
    bean gen
    com.bea.wlw.runtime.core.dispatcher.AppManager - -ensureAppDeployment() valid
    external build, no deployment

    We are definitely not deploying as an EAR and this is not production mode. This
    is happening on our developer workstations as we test on local copies of our application
    running in exploded mode.
    "Cindy McMullen" <[email protected]> wrote:
    The first thing to check is whether your application is deployed as an
    EAR,
    and that you're starting the server in production mode.
    The devs are pretty sure this call is a no-op in production mode -- they'll
    verify and I'll post.
    "Paul Merrigan" <[email protected]> wrote in message
    news:[email protected]...
    We've got a portal application that appears to be constantly checkingfor
    appklication
    deployment, which slows things down significantly.
    We're not sure what we've done, But we get the following messages manytimes (about
    50-60) whenever we hit one of our portal pages:
    com.bea.wlw.runtime.core.dispatcher.AppManager - +ensureAppDeployment()
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - original URL=
    http://localhost:7001/ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - request URI=/ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - context path= /ctdportal
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - servlet path=/appmanager
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - path info=/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - query string= null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - fReadRequest = false
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc requestURI=/ctdportal/framework/skeletons/default/footer.jsp
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc contextpath=/ctdportal
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc servletpath=/framework/skeletons/default/footer.jsp
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc path info=null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - inc query string=null
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - fixed request URL=
    http://localhost:7001/ctdportal/appmanager/ctdportal/public
    com.bea.wlw.runtime.core.dispatcher.HttpRequest - service URL=
    http://localhost:7001/ctdportal/framework/skeletons/default/footer.jsp
    , virtual path= /ctdportal/framework/skeletons/default/footer.jsp ,context path=
    /ctdportal , source path= framework/skeletons/default/footer.jsp ,real
    path=
    >
    C:\DevelCTD81\ctdportalApp\ctdportal\framework\skeletons\default\footer.jsp
    path encoded method name= null , SOAPAction= null , User-Agent=Mozilla/4.0 (compatible;
    MSIE 6.0; Windows NT 5.1; Q312461; GIL 2; .NET CLR 1.0.3705; .NET CLR1.1.4322)
    com.bea.wlw.runtime.core.dispatcher.LoadContext - applicationappDir=C:\DevelCTD81\ctdportalApp
    com.bea.wlw.runtime.core.dispatcher.LoadContext - Valid external build,suppressing
    bean gen
    com.bea.wlw.runtime.core.dispatcher.AppManager - -ensureAppDeployment()valid
    external build, no deployment

  • Is periodic maintenance required for app deployed on OAS on Windows?

    Hi,
    We have an application that uses 7 BPEL processes and one web service deployed on OAS. Application is into production from the last 4 months.
    We are bringing down the App server once in a while due to applying break fixes, etc.
    But, now, considering the App is quite stable, we won't be planning to bring down the app server for few months. My question is, do we need to schedule planned downtime and restart the application server once in a while in view of memory leaks etc as the App is deployed on Windows Operating System?
    It would be a great if I get some info/links that will give me the exact information.
    Thanks,
    Sasi Bhushan.

    Hi Chris,
    Thanks for the reply.
    Yes. Infact we have taken care of log files. But wondering if memory leaks etc could cause total memory consumption and making the app server hung etc.
    So, I am looking for some suggestion on whether we need the app server restart periodically or it's not required at all.
    Thanks,
    Sasi Bhushan.

  • Session Timeout - Process as a webservice

    Hi ,
    I am using ALBPM v5.7.
    In this we are exposing our process as webservice.
    We are Invoking these webservice methods from portal deployed in BEA Weblogic Server,
    The procedure we are following is , starting the session and then invoking our methods -- method1 and method2.
    But , After invoking method1, In the portal, we are waiting for five minutes and then trying to invoke method2 of BPM using the same session,
    When we do this, It is throwing an exception,
    Invalid Session.
    We observed that if we invoke method2 before five minutes then it is working fine.
    So do we have any session timeout for the BPM Process, when we expose our process as a webservice.
    If so , could you please help me in resolving this issue?
    Thanks & Regards,
    Krishnaveni.

    Just input paramters inside the Begin Activity...
    Right Click on the Process and open Process Web-Service and add a Web-Service to it..
    Then start the engine in Studio..
    And then click on Launch Deployed WebServices Webapp..
    And you would get the endpoint..

  • Session Timeout Question in EME

    If I login to eManager Web and instead of logging out I just close the browser will I be logged out? Will the license be released? What is the session timeout for this and is it possible to set this value?

    If you close the browser in e-Manager Enterprise Web instead of logging out there is a TimeOut that will release your license. This can be seen and is reported on in the e-Manager logs. By default the session TimeOut value is 30 minutes. You can find this and/or change this value by opening "<installdir>\Empirix\EmpAppServer\server\default\deploy\jbossweb-tomcat55.sar\conf\web.xml" in a notepad. Once the file is open, go the the ?Default Session Configuration? Section. Here you can change the TimeOut value. You will then need to save the file and restart the Empirix Application Service. The idle sessions are retired after the specified timeout is reached and the licenses are also checked upon this value. I hope this answers your questions.

  • In APEX clicking the hyper link doesn't trigger session timeout page

    Hi All,
    I have a question about the session time out in APEX application. I have created a simple APEX application. In the SQL report region section, i have code like this:
    SELECT DOC_Name, DOC_URL,
    '<a href="' || DOC_URL || ' target="_blank"/">Download file</a>' pdf_link
    FROM test_table
    where emp_number =00010001
    When user clicks on the hyper link, it will display the destination page to user(for example if DOC_URL = 'http://forums.oracle.com', it will display the oracle forum page in a new browser).
    But the issue is that, after user's session timeout (I set for 240 seconds through Shared Components>Edit Security Attributes, i set max the session timeout for example 240 seconds), when i click on this hyperlink, it doesn't trigger my session timeout page and it still displays the page (oracle forum page).
    Why in APEX clicking the hyper link doesn't trigger session timeout page after the user session timeout???
    how to implememt or fix to trigger the session timeout page after clicking on the hyperlinks?
    (BTW, our APEX version is 3.2)
    Thanks!

    Hi Lily,
    the reason for that behavior is that APEX is not involved anymore if you click on an external link. That's completely handled by your browser.
    To involve APEX timeout handling you could redirect to a specific page in your application which performs the final redirect.
    For example:
    1) Create a new page 999
    2) Create hidden page item P999_URL
    3) Create a before header PL/SQL process with the following source
    owa_util.redirect_url('http://'||:P999_URL);
    apex_application.g_unrecoverable_error := TRUE;If you want to embed a link, create a link to page 999 and set the page item P999_URL to forums.oracle.com
    You could also add a white list into the above code to verify that you are just redirecting to valid URLs, so that nobody is using your trusted application URL for phishing attacks.
    Hope that gives you a direction
    Patrick
    Regards
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

  • Increase timeout for bpm workspace

    Please, tell me where can i increase session timeout for bpm workspace (Oracle SOA Suite 11.1.1.4)?
    Thanks.

    Hello Creed -
    Go to the workspace.properties file and edit the following.This is from 10.3.2.
    Hopefully you can found the same in 11 also.
    +# Specifies the timeout period in seconds, between client requests.+
    +# If not specified the default value is 45 minutes.+
    +#fuego.workspace.sessionTimeOut=2700+
    BR,
    Justin.

  • General question re session timeouts

    we'd like to increase the session timeout for our portal from the default 20 min to 60 or so.
    recommendations from plumtree and microsoft suggest that increasing the session timeout (on the server - IIS) to beyond 20 minutes will be detrimental to performance and both advise against it.
    another option would be for users to change their page update settings (through my account -> display options) to say 15 minutes to provide a way of keeping the session alive.
    My question is, isn't this just as much as a performance drain as increasing the session timeout on the server?
    thanks
    Simon Dragicevich

    we'd like to increase the session timeout for our portal from the default 20 min to 60 or so.
    recommendations from plumtree and microsoft suggest that increasing the session timeout (on the server - IIS) to beyond 20 minutes will be detrimental to performance and both advise against it.
    another option would be for users to change their page update settings (through my account -> display options) to say 15 minutes to provide a way of keeping the session alive.
    My question is, isn't this just as much as a performance drain as increasing the session timeout on the server?
    thanks
    Simon Dragicevich

Maybe you are looking for