This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Invalidating HttpSession on JBoss 4.2.2 vs. 5.0.0Beta

 
Oliver Swift
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic