Questions answered
- Site help
- Cascading Style Sheets
- Web fonts
- HTML & XHTML
- Javascript
- Java programming
- Java servlets
- Java servlet API
- Servlet lifecycle
- Java servlet "how to"
- Servlet exceptions
- Servlet threads
- Servlet sessions
- Java Server Pages
- JSP tags & libraries
- Servlet containers
- Site manager
Terms explained
Place your text ad here.
World class Hard Drive Recovery and renowned raid recovery services
WestNIC provides reliable web hosting services
Free software downloads and drivers download resources
This FAQ is part of the Code Style Help and FAQ section. Use the help request form below if your question is not answered here, but make sure you are asking the right question first.
Subscribe to this FAQ: 
Servlet thread implementation
The single thread model
Servlet thread implementation
- Q: Are servlets multi-threaded?
-
A: Yes, servlets are normally multi-threaded. The servlet container allocates a thread for each new request for a single servlet without any special programming. Each thread of your servlet runs as if a single user were accessing it alone, but you can use static variables to store and present information that is common to all threads, like a hit counter for instance.
- Q: How does the container handle concurrent requests?
-
A: Servlet containers usually manage concurrent requests by creating a new Java thread for each request. The new thread is given an object reference to the requested servlet, which issues the response through the same thread. This is why it is important to design for concurrency when you write a servlet, because multiple requests may be handled by the same servlet instance.
The single thread model
- Q: What is the single threaded model?
-
A: Standard servlets are normally handled in a multi-threaded context in the servlet container. A number of virtually simultaneous requests for a single servlet could be handled by different threads using the same servlet instance. Any number of threads could access or modify the static and instance fields of a single servlet instance in an unpredictable sequence. This makes the instance fields of servlets as vulnerable to threading issues as static fields, and modification of shared resources must be considered carefully.
More details available to subscribers:
What is the single threaded model? -
Q: Why use
SingleThreadedModelif servlets are multi-threaded? -
A: The
SingleThreadedModelinterface is used to ensure the safety of servlets that are vulnerable to thread safety issues. Normally, servlets should be written to run safely in a multi-threaded environment, and are executed in this context. TheSingleThreadedModelis a way to override the normal multi-threaded execution context of the servlet container. - Q: How do I implement the single threaded model?
-
A: To create a servlet that a container will manage on a single threaded basis it must declare that it implements the
javax.servlet.SingleThreadModelinterface. This is a marker interface, there are no extra methods to fulfil, but this is sufficient for the container to identify the type and manage it accordingly.public class SingleThreadServlet extends HttpServlet implements SingleThreadServlet { // Standard HTTP servlet methods }The servlet container will typically synchronize access to a single instance of the servlet, or create a pool of servlet instances and allocate one request per instance.
-
Q: Should I use the
SingleThreadedModel? -
A: Not unless you have very good reason. The
SingleThreadedModelinterface has been deprecated, which means that it should not be used and may be removed in a later release of the Java servlet specification and API. It has never really been advisable to implement theSingleThreadedModel, you should always aim to address thread safety issues in servlets using standard Java programming techniques. -
Q: How can I invoke servlet pooling with
SingleThreadedModel? -
A: The
SingleThreadedModelservlet specification does not require the creation of a pool of servlets. A single threaded model implementation may also synchronize access to a single servlet instance to achieve the same outcome, so that only one request is processed at a time. Apache Tomcat uses the synchronized approach, other servlet containers may use the pooled approach.If you are concerned about the performance impact of synchronized access to the servlet instance, it would be preferable to re-design your servlet so that it does not depend on this mechanism at all. For example, you might create a synchronized block around the statements that are vulnerable to threading issues. By doing away with the single threaded model, you will minimise the performance impact of thread control.
| Front-end FAQs | Back-end FAQs | Learning Java |
|---|---|---|
See site help for questions about this site, our text ads and sponsored links services.
