Shulou(Shulou.com)06/02 Report--

This article mainly introduces "what is the life cycle of Servlet container". In daily operation, I believe many people have doubts about what the life cycle of Servlet container is. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful for you to answer the question of "what is the life cycle of Servlet container?" Next, please follow the editor to study!

Servlet is a general extension of servers that support Java. Its most common use is to extend Web servers, providing very secure, portable, and easy-to-use alternatives to CGI. It is a dynamically loaded module that serves requests from Web servers. It runs completely on the Java virtual machine. Because it runs on the server side, it does not rely on browser compatibility.

Servlet container:

Responsible for processing the customer request, sending the request to Servlet and returning the result to the customer. The actual implementation of the container for different programs may vary, but the interface between the container and Servlet is defined by Servlet API, which defines the methods to be called by the Servlet container on Servlet and the object classes passed to Servlet.

Servlet Lifecycle:

1. Servlet container creates an instance of Servlet

2. The container calls the init () method of the instance

3. If the container has a request for the Servlet, call the service () method of this instance

4. The container calls its destroy () method before destroying the instance

5. Destroy and mark the instance for garbage collection

Once a Servlet is requested, there is no way to prevent the container from performing a full life cycle.

The container creates an instance of Servlet*** when it is called and keeps the instance in memory, allowing it to process all requests. The container can decide to remove this instance from memory at any time. In a typical model, the container creates a separate instance of each Servlet. Instead of creating a new thread for each request, the container uses a thread pool to dynamically allocate threads to incoming requests, but from Servlet's point of view, the effect is the same as creating a new thread for each request.

At this point, the study of "what is the life cycle of Servlet containers" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.