Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #34017

Re: ExecutorService.shutdown ambiguity

Show all headers | View raw

On Fri, 18 Mar 2016 12:37:13 -0700, Roedy Green wrote:

> Here is the JavaDoc for ExecutorService.shutdown.
> To me it is ambiguous. How do you read it?
> 
> What happens to a task in queue? 

"... previously submitted tasks are executed ..."

> What happens to a task that is executing?

Presumably it continues executing.
However ExecutorService.shutdown() returns without awaiting completion.
 
> 
>      * Initiates an orderly shutdown in which previously submitted *
>      tasks are executed, but no new tasks will be accepted.
>      * Invocation has no additional effect if already shut down.
>      *
>      * <p>This method does not wait for previously submitted tasks to *
>      complete execution.  Use {@link #awaitTermination
> awaitTermination}
>      * to do that.
>      *
>      * @throws SecurityException if a security manager exists and *     
>         shutting down this ExecutorService may manipulate *        
>      threads that the caller is not permitted to modify *        
>      because it does not hold {@link *        
>      java.lang.RuntimePermission}{@code ("modifyThread")}, *         or
>      the security manager's {@code checkAccess} method *         denies
>      access.
>      */
>     void shutdown();

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ExecutorService.shutdown ambiguity Roedy Green <see_website@mindprod.com.invalid> - 2016-03-18 12:37 -0700
  Re: ExecutorService.shutdown ambiguity Jeff Higgins <jeff@invalid.invalid> - 2016-03-18 20:52 +0000
  Re: ExecutorService.shutdown ambiguity v_borchert@despammed.com (Volker Borchert) - 2016-03-18 20:20 +0000
  Re: ExecutorService.shutdown ambiguity Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2016-03-19 23:07 -0700

csiph-web