Tomcat session tracking
21 September, 2010
Tomcat's default method of tracking user sessions is by using Cookies. This provides a neat way of keeping track of sessions while remaining invisible to the end-user. One drawback of this method is that Cookies are shared across multiple tabs within a browser instance. This means that you cannot open two tabs and log in to Yellowfin twice in the same browser - Tomcat will identify them both as the same session, and the second login will override the first.
Tomcat can be configured to track sessions by using "URL rewriting" - adding a session id parameter to every URL. This means that each tab will get it's own session id, allowing them to operate independently. You will see the jsessionid parameter in the address bar of your browser:
To use URL rewriting instead of Cookies, edit the file:
Yellowfin/appserver/conf/Catalina/localhost/ROOT.xml
In the Context element, add the attribute cookies="false". For example:
[code]
<Context docBase="/yellowfin/yellowfin.war" path="" privileged="false"
reloadable="true" swallowOutput="false" useNaming="true"
cookies="false">
[/code]
Restart Yellowfin to pick up this change.
Steve
Tomcat can be configured to track sessions by using "URL rewriting" - adding a session id parameter to every URL. This means that each tab will get it's own session id, allowing them to operate independently. You will see the jsessionid parameter in the address bar of your browser:

To use URL rewriting instead of Cookies, edit the file:
Yellowfin/appserver/conf/Catalina/localhost/ROOT.xml
In the Context element, add the attribute cookies="false". For example:
[code]
<Context docBase="/yellowfin/yellowfin.war" path="" privileged="false"
reloadable="true" swallowOutput="false" useNaming="true"
cookies="false">
[/code]
Restart Yellowfin to pick up this change.
Steve