本文整理匯總了Java中org.directwebremoting.extend.ServerLoadMonitor.shutdown方法的典型用法代碼示例。如果您正苦於以下問題：Java ServerLoadMonitor.shutdown方法的具體用法？Java ServerLoadMonitor.shutdown怎麽用？Java ServerLoadMonitor.shutdown使用的例子？那麽, 這裏精選的方法代碼示例或許可以為您提供幫助。您也可以進一步了解該方法所在類org.directwebremoting.extend.ServerLoadMonitor的用法示例。
在下文中一共展示了ServerLoadMonitor.shutdown方法的3個代碼示例，這些例子默認根據受歡迎程度排序。您可以為喜歡或者感覺有用的代碼點讚，您的評價將有助於係統推薦出更棒的Java代碼示例。
示例1: shutdownServerLoadMonitorsInContainerList
import org.directwebremoting.extend.ServerLoadMonitor; //導入方法依賴的package包/類
/**
* Internal use only.
* <p>If we detect that the server is being shutdown then we want to kill
* any reverse ajax threads.
* @param containers The list of containers to look for ServerLoadMonitors in
* @param title What causes this (for debug purposes)
*/
public static void shutdownServerLoadMonitorsInContainerList(List containers, String title)
{
if (containers == null || containers.size() == 0)
{
log.debug("No containers to shutdown for: " + title);
return;
}
log.debug("Shutting down containers for: " + title);
for (Iterator it = containers.iterator(); it.hasNext();)
{
Container container = (Container) it.next();
ServerLoadMonitor monitor = (ServerLoadMonitor) container.getBean(ServerLoadMonitor.class.getName());
monitor.shutdown();
}
}
示例2: shutdown
import org.directwebremoting.extend.ServerLoadMonitor; //導入方法依賴的package包/類
/**
* Kill all comet polls.
* <p>Technically a servlet engine ought to call this only when all the
* threads are already removed, however at least Tomcat doesn't do this
* properly (it waits for a while and then calls destroy anyway).
* <p>It would be good if we could get {@link #destroy()} to call this
* method however destroy() is only called once all threads are done so it's
* too late.
*/
public void shutdown()
{
ServerLoadMonitor monitor = (ServerLoadMonitor) container.getBean(ServerLoadMonitor.class.getName());
monitor.shutdown();
}
示例3: shutdown
import org.directwebremoting.extend.ServerLoadMonitor; //導入方法依賴的package包/類
/**
* Kill all comet polls.
* <p>Technically a servlet engine ought to call this only when all the
* threads are already removed, however at least Tomcat doesn't do this
* properly (it waits for a while and then calls destroy anyway).
* <p>It would be good if we could get destroy() to call this
* method however destroy() is only called once all threads are done so it's
* too late.
*/
public void shutdown() {
ServerLoadMonitor monitor = (ServerLoadMonitor) container.getBean(ServerLoadMonitor.class.getName());
monitor.shutdown();
}