Improve the API for controlling and managing operating-system processes.
The limitations of the current API often force developers to resort to
Java SE provides limited support for native operating-system processes.
It provides a basic API to setup the environment and start a process.
The process streams can, since Java SE 7, be redirected to files, pipes,
or can be inherited. Once started, the API can be used to destroy the
process and/or wait for the process to terminate.
The java.lang.Process class is enhanced to provide the operating specific
process id of the process, information about the process including
the arguments, the command, the start time of the process, the accumulated
cpu time of the process and the user name for the process.
The java.lang.ProcessHandle class returns information about each process
as provided by the operating system including process id, arguments, command,
start time, etc. A ProcessHandle can return the process' parent, and the direct children,
and to all descendants via a stream of ProcessHandles.
ProcessHandles can be used to destroy processes and monitor process liveness.
With ProcessHandle.onExit, the asynchronous mechanisms of CompletableFuture
can be used to schedule an action to be taken when the process exits.
Access to information about processes and control of processes is subject to security
manager permissions and are limited by the normal operating system access controls.
The classes or methods introduced will require new unit tests that can be
developed along with the implementation. More functional tests would be
Risks and Assumptions
The main risk with this API is differences between operating systems, in
The design of this API needs to accommodate possible deployment on
smaller devices with different operating system models. It should also
take into account environments where multiple Java virtual machines are
running in the same operating system process. These considerations could
lead to a more abstract API and/or increase the design effort.