classBlockingProcess extends Actor with ActorLogging
This actor uses the JDK process API. As such, more memory given that more threads are consumed. Favor the
NonBlockingProcess actor unless you *need* to use the JDK.
BlockingProcess encapsulates an operating system process and its ability to be communicated with via stdio i.e.
stdin, stdout and stderr. The reactive streams for stdio are communicated in a BlockingProcess.Started event
upon the actor being established. The parent actor is then subsequently streamed
stdout and stderr events. When the process exists (determined by periodically polling process.isAlive()) then
the process's exit code is communicated to the receiver in a BlockingProcess.Exited event.
A dispatcher as indicated by the "akka.process.blocking-process.blocking-io-dispatcher-id" setting is used
internally by the actor as various JDK calls are made which can block.
This actor uses the JDK process API. As such, more memory given that more threads are consumed. Favor the NonBlockingProcess actor unless you *need* to use the JDK.
BlockingProcess encapsulates an operating system process and its ability to be communicated with via stdio i.e. stdin, stdout and stderr. The reactive streams for stdio are communicated in a BlockingProcess.Started event upon the actor being established. The parent actor is then subsequently streamed stdout and stderr events. When the process exists (determined by periodically polling process.isAlive()) then the process's exit code is communicated to the receiver in a BlockingProcess.Exited event.
A dispatcher as indicated by the "akka.process.blocking-process.blocking-io-dispatcher-id" setting is used internally by the actor as various JDK calls are made which can block.