-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mauro,
On 11/10/2009 4:44 PM, mauroS wrote: > I run jbossweb-tomcat55.sar inside jboss-4.0.5.CR1 > > I have one EAR file with two WAR files inside. > > I added HttpSessionListener in web.xml to both wars. > > If I request both war files from the same browser I have two HttpSession > objects with different hash but with the same sessionID. That is exacly what > I expected. What do you mean "different hash"? If you have a single session id, I would expect that you'd only one session. > but sessionDestroyed is only called for the first HttpSession object and > never for the second ! This is what I would expect if there is only one session. I don't know how JBoss handles multiple WARs in EAR files (I'm not familiar with the specs for EAR deployment), but it's possible that this is intended behavior. Do you have documentation which suggests this is /not/ correct behavior? > furthermore sessionDestroyed is never called again for this sessionID also > if new HttpSessions with new hash and same sessionID are created ! Again, what is this "hash" thing? Session ids shouldn't be re-used... at least not for a very long time. > If I request the war file with the "not destroyed session object" again, > there is never a new session created. So, the sessionDestroyed method is called, yet the session appears to continue to live and be accessible? Yikes. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr54hUACgkQ9CaO5/Lv0PBWCwCeILogm+f3BMEbjvVGOVmGDTjU fFAAoJe+RgjaomSw4eoJKSxDS62t/1Jl =h1y1 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
