[
https://issues.jboss.org/browse/WFCORE-1147?page=com.atlassian.jira.plugi...
]
David Lloyd commented on WFCORE-1147:
-------------------------------------
Because it's reliable i.e. there are fewer failure states. We don't have to worry
about re-establishing if the child gets "lost". If the output-to-stdin stream
hangs or dies, we can just immediately kill the child process because it's very, very
likely to be a catastrophic error. If the return-to-server dies, we can continue passing
orders to the client, including instructions for re-connecting the result stream.
From the client perspective, if the stream-from-server ends, we exit
immediately (with an exit code that communicates what happened to the server). If the
stream-to-server dies, we just close it down and await new connect instructions, possibly
buffering operation results in the meantime. This helps to ensure that no zombie servers
will survive after the HC dies, which is AFAICT the most correct/reliable behavior.
Eliminate ProcessController
---------------------------
Key: WFCORE-1147
URL:
https://issues.jboss.org/browse/WFCORE-1147
Project: WildFly Core
Issue Type: Task
Components: Server
Reporter: David Lloyd
We should eliminate ProcessController and directly have the HC control the servers. This
should greatly simplify the code and add more power and flexibility to the management and
lifecycle of server JVMs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)