> From: Markus Reis [mailto:[EMAIL PROTECTED] > Subject: Re: RE: multiple Set-Cookie headers in initial http response > > I have the impression that this happens already before the > webapp comes into play, because the HttpSessionListener > implementation prints out those "Session created | destroyed" > events before the NewSession servlet is even entered.
The webapp (including filters and JSPs, not just servlets) can create and invalidate sessions at its whim; each such event will trigger a call to the HttpSessionListener. > It seems to be some component in Tomcat (or JBoss) that acts in > front of the Servlet and creates those sessions (per request > parameter). Then why is it happening only with *your* webapp and not to the millions of other webapps deployed on Tomcat and JBoss? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
