WebSphere Application Server & Liberty

 View Only

  • 1.  Respawning of the expired sessions

    Posted Wed August 25, 2021 10:22 AM
    Hi All,

    I am currently working on WebSphere Network Deployment of version 9.0.0.11.

    We are facing a problem as sessions are getting expired  And when new messages are incoming, new sessions are being created which is results in the timeout for the interface components expecting a response within a short timespan. Since sessions creating in WebSphere is taking some additional time, it is resulting in the timeout to ESB waiting for response. 

    Just want to clarify is there any option in WebSphere so that session which is expired can respawn on its own immediately rather than creating a new session during any incoming message.

    Much Thanks in advance.
    Sam

    ------------------------------
    Emilsingh Samuel
    ------------------------------


  • 2.  RE: Respawning of the expired sessions

    IBM Champion
    Posted Thu August 26, 2021 02:12 AM
    Hello Emilsingh,
    well, sessions are setup with a inactivity interval. I.e. if a session object is not used for a specific period it is marked as expired and becomes eligible for a cleanup by the session cleanup thread. Therefore once a session is expired there is no way to reliably say that the session data is still available. What I've seen at some customers sites is that there is a little piece of JavaScript running in the users browser which sends a "ping" request to the server after a certain time of inactivity to keep the session alive.

    If you mention that "results in the timeout for the interface components expecting a response within a short timespan" - what is the time-span we are talking about? Well, sure session creation takes some time, but are you sure it is the root cause of the ESB timeout? How long does the session creation take time? What are the session settings? 

    Hope that helps.

    Kind regards and have a good day - Hermann
    ​

    ------------------------------
    Hermann Huebler
    2innovate IT Consulting GmbH
    Vienna
    Austria

    #IBMChampion
    ------------------------------

    Original Message


  • 3.  RE: Respawning of the expired sessions

    Posted Thu August 26, 2021 06:30 AM
    Hi, I hope you are talking about the JSESSIONID, as it is unclear why something that takes a few ms to create would be causing a timeout unless the application is populating it with data.  You can set WebSphere to reuse the session id with a custom property, but the data inside of it will be gone.  The default session timeout is 30 minutes and this would mean that the user was not using their application for more than the session timeout.

    Brian

    ------------------------------
    Brian S Paskin
    Sr. WebSphere, Liberty and MQ Architecture
    Cloud Automation
    IBM Expert Labs
    ------------------------------

    Original Message