0

Running our JRuby/Rails application locally on rails/rack, the session id is reset/renewed in session/abstract_store.rb using the DestroyableSession destroy method. Each new request coming in, using the same browser, will generate a new session id.

When the application is deployed to Tomcat and a request is completed. If the same browser window is used and a subsequent transaction is submitted, the session id remains the same between transactions and no new session id is created.

How does running on Tomcat cause the difference in session handling?

user1729188
  • 1
  • 1

1 Answers1

0

Tomcat is a servlet container designed to solve these problems for you. In particular it sets the JSESSIONID cookie to track the current session from the user.

Ari Maniatis
  • 8,038
  • 3
  • 19
  • 28