Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are many things which can make a session disappear. I'd suggest to track them and verify if anything went right. This is easier to do if you <a href="https://stackoverflow.com/questions/3106452/java-servlet-instantiation-and-session-variables/3106909#3106909">understand</a> how sessions work.</p> <ul> <li><p>Session has been timed out. This usually defaults to 30 minutes. This is confiugureable by <code>&lt;session-timeout&gt;</code> in <code>web.xml</code> where you can specify the timeout in minutes. You can implement a <a href="http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpSessionListener.html" rel="nofollow noreferrer"><code>HttpSessionListener</code></a> to track session creation and destroy using a logger.</p></li> <li><p>Session has forcibly been invalidated. This happens when the code calls <a href="http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpSession.html#invalidate--" rel="nofollow noreferrer"><code>HttpSession#invalidate()</code></a>. This is trackable with a <code>HttpSessionListener</code> as well.</p></li> <li><p>Session cookie has been disappeared. Sessions are backed by cookies. If a session is been created, the server will add a <code>Set-Cookie</code> header with session ID. The client should send the same cookie back as <code>Cookie</code> header in all subsequent requests on the (context) path as specified in the <code>Set-Cookie</code> header. This is trackable in the HTTP traffic monitor ("Network" tab) of browser's builtin web developer toolset (press F12 in Chrome/Firefox23+/IE9+). Cookies are accessible for all webapps on the same cookie domain. Also, if <code>ServletC2</code> runs on a different webapp context than <code>ServletC1</code>, then it won't use the same session. Further, if the "server" webapplication runs on the same domain, then it's in theory able to wipe out all cookies of the "client" webapplication.</p></li> <li><p>The client doesn't support cookies. A well designed webapplication uses URL rewriting with <code>jsessionid</code> to track cookieless clients between requests on the same webapplication. But the second webapplication has to do the same when redirecting back to the first webapplication.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload