Before taking a dive in the session control in the Tomcat, take a look on the basics of the session. An HTTP session is a consecutive interactions between a single browser instance and a web server all across. an http Session object temporarily stores information about a user, including a unique session identifier and references to Java objects that the web application stores as attributes of the session in later stages of functions. A Session Manager implements persistent storage for their sessions, regardless of whether they use the Store interface or not.
Session manager works in the similar fashion as quoted below :
< Manager className="some.manager.implementation.className"
customAttribute1=”some custom value”
customAttribute2=”some other custom value”