Any resources that this servlet might hold have been released.
False: destroy() gives the servlet an opportunity to clean up any resources that are being held.
The servlet container time out has exceeded for this servlet instance.
Partly true. Another reason is that all threads within the servlet's service method have exited.
The init() method has been called on this instance
True: If init didn't work, then there would not be a servlet in service to start with.
None of the requests can EVER be serviced by this instance
True, the servlet container will not call the service method again on this servlet.
All threads created by this servlet are done
Partly true. Another reason is that a timeout period has passed. This may have been set in the deployment descriptor like this (for 30 minutes):
<session-config>
<session-timeout>30</session-timeout>
</session-config>
Also, the HttpSession interface has a method to set a session invalidated period (in seconds):
setMaxInactiveInterval(3600)
[ September 24, 2003: Message edited by: Roger Chung-Wee ]