JBossWeb/Tomcat HTTP Session Implementation Details: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 22: Line 22:
* The <tt>Session</tt> is looked up in the <tt>sessions</tt> map by its session ID. This applies to both non-clustered and clustered sessions. If found, it is returned.  
* The <tt>Session</tt> is looked up in the <tt>sessions</tt> map by its session ID. This applies to both non-clustered and clustered sessions. If found, it is returned.  
* If no session is found, and <tt>org.apache.catalina.connector.Request.SESSION_ID_CHECK</tt> is true, the request tries to find the session with the ID equals to requestedSessionId among the Host's children.
* If no session is found, and <tt>org.apache.catalina.connector.Request.SESSION_ID_CHECK</tt> is true, the request tries to find the session with the ID equals to requestedSessionId among the Host's children.
** If no session is found, the <tt>Manager</tt> instance is messaged to <tt>createSession(sessionId)</tt>.
* If no session is found, the <tt>Manager</tt> instance is messaged to <tt>createSession(sessionId)</tt>.
** Once the session is created by the manager (and its id generated), the request then sets a "session" cookie on Response "Set-Cookie" "JSESSIONID=FFB6...56; Path=/mycontext". The internal implementation of the cookie is <tt>TomcatCookie</tt>.
* Once the session is created by the manager (and its id generated), the request then sets a "session" cookie on Response "Set-Cookie" "JSESSIONID=FFB6...56; Path=/mycontext". The internal implementation of the cookie is <tt>TomcatCookie</tt>.


=SessionID Generation=
=SessionID Generation=

Revision as of 19:17, 15 July 2016

Internal

Relevance

  • EAP 6.4.6
  • JBoss AS 5.1.2

Lifecycle

Each org.apache.catalina.connector.Request maintains a direct reference to the active Session instance the request belongs to. The reference can be null.

The repository of sessions for a specific application (context) is an instance of org.apache.catalina.Manager. The manager is referred to from the StandardContext via the manager reference.

  • If the application is not clustered, the Manager implementation is an org.apache.catalina.session.StandardManager.
  • If the application is clustered, the Manager implementation is an org.jboss.as.web.session.DistributableSessionManager.

Sessions are not created automatically by the Tomcat machinery, unless we invoke HttpServletRequest.getSession() (which is equivalent with HttpServletRequest.getSession(true)) or org.apache.catalina.connector.Request.getSessionInternal().

When HttpServletRequest.getSession() is invoked, the following happen:

  • The Manager instance is obtained from the StandardContext associated with the request.
  • Manager.findSession(sessionId) is messaged on the Manager instance.
  • The Session is looked up in the sessions map by its session ID. This applies to both non-clustered and clustered sessions. If found, it is returned.
  • If no session is found, and org.apache.catalina.connector.Request.SESSION_ID_CHECK is true, the request tries to find the session with the ID equals to requestedSessionId among the Host's children.
  • If no session is found, the Manager instance is messaged to createSession(sessionId).
  • Once the session is created by the manager (and its id generated), the request then sets a "session" cookie on Response "Set-Cookie" "JSESSIONID=FFB6...56; Path=/mycontext". The internal implementation of the cookie is TomcatCookie.

SessionID Generation

SessionID is generated by ManagerBase.generateSessionId().

Session Counter

Maintained by the sessionCounter variable of the StandardManager instance of the web application.

Session Replication

Retrieved from "https://kb.novaordis.com/index.php?title=JBossWeb/Tomcat_HTTP_Session_Implementation_Details&oldid=10192"