Http Session is not destroyed when redeploying war-archive

[zarni]

I have encountered a problem in jboss 3.2.5, actually tomcat 5.
When I redeploy a war archive with my web-application, the sessions, if any opened by clients, don't get destroyed, they live on. The problem is all attributes stored in the
session object are lost and the application doesn't work no more.
I have to shutdown my webbrowser and run it again, so that a fresh session is created, then
it works.

This was not a problem with tomcat 4.

Are there any options I could set and disable this.
Or is this a BUG.

Anything?

Thank's very much.

[zarni]

I did some research and found out that tomcat 5 is using a Manager to persist
http sessions. All attributes put in the session should be java.io.Serializable.

I just don't wont this,
so is there a way to disable session persistence in tomcat 5 and jboss3.2.5?

thanks

[trickal]

Hi Zarni,

maybe the following links are helpful for your research:

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=51689
http://sourceforge.net/tracker/index.php?func=detail&aid=986585&group_id=22866&atid=376687
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html

Thomas

[trickal]

Hi Zarni,

i just stumbled accross some additional information. The patch of Mikko Koponen was integrated in JBoss 3.2.6RC1:

http://sourceforge.net/docman/display_doc.php?docid=23847&group_id=22866

If you change to JBoss 3.2.6 you may configure a session manager for your web application in WEB-INF/context.xml. Look here for information about how to do this:

http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html

Thomas

[trickal]

Hi Zarni,

here is an example for WEB-INF/context.xml that disables session persistence:

<Context path="">
 <Manager className="org.apache.catalina.session.StandardManager" pathname="" />
</Context>

Thomas

[zarni]

Thank you trickal!

I have been using jboss3.2.6 for a long time now, and it is working very fine with the
default context manager (I made all my objects serializable, and the sessions persist fine without any errors). But your reply gave me some ideas on doing some custom
context managers that will simplify the development of my web apps (custom logging, login, custom resources and stuff).

Thanks again!