• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

HttpSessionEvent - Propagated across JVM?

 
Ranch Hand
Posts: 230
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Does the HttpSessionEvent propagate to the other JVM on a session migration?

HttpSession gets migrated from one JVM to another and this is possible. At this time the HttpSessionActivationListener gets notified.

When the session gets migrated, the sessionDidActivate will be called on the target m/c JVM. Am I Right?

If that is the case, will the same HttpSessionEvent is propagated (OR) It is a fresh HttpSessionEvent and a fresh Listener instance in the target JVM, that comes into action?
 
Bartender
Posts: 6663
5
MyEclipse IDE Firefox Browser Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The HttpSession is propagated not the HttpSessionEvent. It is the same thing not a completely fresh session. Imagine if your session were to shift when you shopped and you lost all your items. That would be terrible. It is advisable to mark those objects bound to a session as Serializable.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic