How many instances created in the WebContainer
When the Servlet container starts, it:
- reads
web.xml
; - finds the declared Servlets in the classpath; and
- loads and instantiates each Servlet only once.
Roughly, like this:
String urlPattern = parseWebXmlAndRetrieveServletUrlPattern();
String servletClass = parseWebXmlAndRetrieveServletClass();
HttpServlet servlet = (HttpServlet) Class.forName(servletClass).newInstance();
servlet.init();
servlets.put(urlPattern, servlet); // Similar to a map interface.
Those Servlets are stored in memory and reused every time the request URL matches the Servlet's associated url-pattern
. The servlet container then executes code similar to:
for (Entry<String, HttpServlet> entry : servlets.entrySet()) {
String urlPattern = entry.getKey();
HttpServlet servlet = entry.getValue();
if (request.getRequestURL().matches(urlPattern)) {
servlet.service(request, response);
break;
}
}
The GenericServlet#service()
on its turn decides which of the doGet()
, doPost()
, etc.. to invoke based on HttpServletRequest#getMethod()
.
You see, the servletcontainer reuses the same servlet instance for every request. In other words: the servlets are shared among every request. That's why it's extremely important to write servlet code the threadsafe manner --which is actually simple: just do not assign request or session scoped data as servlet instance variables, but just as method local variables. E.g.
public class MyServlet extends HttpServlet { private Object thisIsNOTThreadSafe; protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
Object thisIsThreadSafe; thisIsNOTThreadSafe = request.getParameter("foo"); // BAD!! Shared among all requests!
thisIsThreadSafe = request.getParameter("foo"); // OK, this is thread safe.
}
}
(Comments: I will just add that if the same servlet class is mapped to two different urls in web.xml, then two instances are created. But the general principle still holds, one instance serves multiple requests.)
There is only one instance of the servlet which is reused for multiple requests from multiple clients. This leads to two important rules:
- don't use instance variables in a servlet, except for application-wide values, most often obtained from context parameters.
- don't make methods
synchronized
in a servlet
(same goes for servlet filters and jsps)
According to the Java Servlet Specification Version 3.0 (pp. 6-7), there will be one instance per declaration per JVM
最新文章
- linux限制ftp账户的访问路径
- 【收藏】Android AutoLayout全新的适配方式, 堪称适配终结者
- Linux下开发常用 模拟 Http get和post请求
- Android--Retrofit+RxJava(二)
- Error: Error #2014: Feature is not available at this time. at flash.filesystem::File$/initDocumentsDir()
- Linux启动/停止/重启Mysql数据库的方法——转载
- MySQL5.5半同步模式
- ios开发之网络基础
- photoshop:多边形选项
- spoj PARTIT
- 华为S5300交换机配置基于接口的本地端口镜像
- gulp4个基础API
- DNS没有生效的几个原因
- mybatis入门-框架原理
- Java IO学习笔记二
- Rx 入门指引 (一)
- http和https区别及概念
- springboot整合mybatis出现的一些问题
- 如何在IDEA里给大数据项目导入该项目的相关源码(博主推荐)(类似eclipse里同一个workspace下单个子项目存在)(图文详解)
- Linux环境下运行简单java程序