For SingleThreadModel servlets, containers may follow one of the following approaches to ensure that each sevlet instance is invoked in a separate thread:

Instance Pooling :
in this approach, the container maintains a pool of servlet instances. For each incoming request, the container allocates a servlet instance from the pool, and upon completion of the service, the container returns the instance to the pool.

Request Serialization :
in this approach, the container maintains a single instance of the servlet. However since the container cannot send multiple requests to the instance at the same time, the container serialize the requests. This means that new requests will be kept waiting while the current request is being served.

a combination of these two approaches is more pragmatic, so that the container could maintain a reasonable member of instances in the pool, while still serializing requests if the number of requests exceeds the number of instance in the pool.

_____________________
Submitted by abhishek trivedi (imabhishekin@gmail.com)
Source: CoolInterview.com

• There should not be any Spelling Mistakes.
• There should not be any Gramatical Errors.
• Answers must not contain any bad words.
• Answers should not be the repeat of same answer, already approved.
• Answer should be complete in itself.

Post your answer here

Name *

Email Id *

Answer *

Verification Code *

Not readable? Load New Code

Inform me about updated answers to this question.