@Override
	public void contextDestroyed(ServletContextEvent contextEvent) {
		log.debug("Context |%s| destroying.", appName);
		try {
			destroy();
		} catch (Throwable t) {
			log.dump(String.format("Fatal error on container |%s| destroy:", appName), t);
		}
	}
@Override
	public void contextDestroyed(ServletContextEvent contextEvent) {
		log.debug("Context |%s| destroying.", appName);
		try {
			destroy();
		} catch (Throwable t) {
			log.dump(String.format("Fatal error on container |%s| destroy:", appName), t);
		}
	}
@ Override public void contextDestroyed ( ServletContextEvent contextEvent ) { log . debug ( "Context |%s| destroying." , appName ) ; try { destroy ( ) ; } catch ( Throwable t ) { log . dump ( String . format ( "Fatal error on container |%s| destroy:" , appName ) , t ) ; } }
Release resources used by this tiny container instance. After execution this method no HTTP requests can be handled.
<p>
<b>Implementation note:</b> tiny container destruction logic is based on assumption that this
<code>contextDestroyed</code> handler is called after all web application's servlets destruction. Here is the relevant
excerpt from API-DOC: <em>All servlets and filters have been destroy()ed before any ServletContextListeners are notified
of context destruction.</em>

@param contextEvent context event provided by servlet container.
Release resources used by this tiny container instance . After execution this method no HTTP requests can be handled . <p > <b > Implementation note : < / b > tiny container destruction logic is based on assumption that this <code > contextDestroyed< / code > handler is called after all web application s servlets destruction . Here is the relevant excerpt from API - DOC : <em > All servlets and filters have been destroy () ed before any ServletContextListeners are notified of context destruction . < / em >