Well, I think there's one session for the servlet itself, which handles
the many SOAP requests without spawning itself (another servlet
instance) in the process. I believe the statelessness of the SOAP calls
is mandated in the JAX-WS specification. Our servlets[1] extend the
Java EE's HttpServlet, I don't know of the mechanism to ensure that
multiple sessions are not created, someone on the Tomcat team might be
able to answer.
Glen
[1]
http://svn.apache.org/viewvc/cxf/trunk/rt/transports/http/src/main/java/org/apache/cxf/transport/servlet/
On 10/10/2011 12:33 PM, David Sills wrote:
The real question is, does the Tomcat container know that? It's just
another request to it, I would have thought. I'm trying to avoid the
overhead, as my application may have very heavy load initially.
-----Original Message-----
From: Glen Mazza [mailto:[email protected]]
Sent: Monday, October 10, 2011 12:16 PM
To: [email protected]
Subject: Re: Tomcat session invalidation
That shouldn't be a concern, as SOAP requests are all stateless by
default (have REQUEST scope).
Glen
On 10/10/2011 10:39 AM, David Sills wrote:
All:
I'm a little confused about something. I'm using Tomcat as my servlet
(web-service) container with CXF and want to ensure that web service
requests do not create HTTP sessions. I cannot seem to find
documentation about this, even on the Tomcat site - maybe there isn't
a
way to do it?
Does anyone have any suggestions?
David Sills
--
Glen Mazza
Talend - http://www.talend.com/apache
Blog - http://www.jroller.com/gmazza
Twitter - glenmazza
