*
The moose likes Servlets and the fly likes Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » Servlets
Bookmark "Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta" Watch "Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta" New topic
Author

Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta

Oliver Swift
Greenhorn

Joined: Apr 17, 2008
Posts: 3
Hello everyone

I am an absolute beginner at servlet programming.
I'm having a hard time figuring out why the HttpSession.invalidate() method behaves differently on JBoss 4.2.2GA and 5.0.0Beta4.

My servlet is very simple:



When deployed to JBoss 5 I get what I expect: Every time I click the browser's reload button a different ID is printed out. (This also happens when I deployed the servlet to Tomcat 6). So far so good.

But when deployed to JBoss 4.2.2 the session ID does not change when the reload button is clicked. So I guess the session doesn't really gets invalidated.

Could anybody please give me some hints why this is could be happening? Is there some configuration I'm missing with JBoss 4.2.2?

Thanks in advance
Oliver
 
Consider Paul's rocket mass heater.
 
subject: Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta