JEP 102: Process API Updates

AuthorAlan Bateman
OrganizationOracle
Created2011/9/1
Updated2013/12/12
TypeFeature
StateCandidate
Componentcore/libs
ScopeSE
RFE4076796 (4333183, 4890847, 6447323)
Internal-refsOracle:A360:533757, Oracle:jplan:005
Discussioncore dash libs dash dev at openjdk dot java dot net
EffortM
DurationM
Endorsed-byBrian Goetz

Summary

Improve the API for controlling and managing operating system processes.

Motivation

Long-standing shortcoming in the platform, requiring applications to resort to native code. Long requested by developers.

Description

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.

Many enterprise applications and containers involve several Java virtual machines and processes and have long-standing needs which include:

Testing

The classes or methods introduced will require new unit tests that can be developed along with the implementation. More functional tests would be useful too.

Risks and Assumptions

The main risk with this API is differences between operating systems (Windows in particular).

The design of this API needs to take 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 require result in a more abstract API and/or increase the design effort.

Impact