In order to disable the tomcat persistent session, I made the following change to the bundled tomcat configuration and it seems to work well for me.
In the file deploy/jbossweb-tomcat50.sar/server.xml, change the existing DefaultContext element so that it looks as follows:
<DefaultContext cookies="true" crossContext="true" override="true"> <Manager classname="org.apache.catalina.session.StandardManager" pathname="" /> </DefaultContext>
Setting the pathname attribute to null tells the StandardManager (default Tomcat session manager) that session persistence is not desired. This is as per the Tomcat API documentation, see method setPathName of class StandardManager: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/catalina/docs/api/org/apache/catalina/session/StandardManager.html#getPathname()
You may also want to note that prior to JBoss 3.2.5, the server.xml configuration did not exist and the
Tomcat server configuration parameters had to be defined in the jboss-service.xml file located in the META-INF directory of the bundle tomcat SAR.
Thanks for your answer !
I have tried this setting and it did'nt work. After your answer i try again but still no luck.
I read a patch for managing context on sourceforge http://sourceforge.net/tracker/index.php?func=detail&aid=986585&group_id=22866&atid=376687. Is it related ?
I wasn't aware of this add-on patch related to context management for JBoss 3.2.5. Thanks for pointing this out, I'll look into it.
From the looks of it, the package makes it possible to configure the context per web app (as opposed to just for the default Tomcat context).
What I'm not clear on is whether configuration of the default Tomcat context should work 'out of the box' for JBOSS 3.2.X or whether this add-on patch is also necessary. Does anyone have any info on this?