source: main/trunk/greenstone3/src/java/org/greenstone/util/SafeProcess.java@ 31716

Last change on this file since 31716 was 31716, checked in by ak19, 7 years ago

Comments adjusted

File size: 65.1 KB
Line 
1package org.greenstone.util;
2
3import java.io.BufferedReader;
4import java.io.BufferedWriter;
5import java.io.Closeable;
6import java.io.File;
7import java.io.InputStream;
8import java.io.InputStreamReader;
9import java.io.IOException;
10import java.io.OutputStream;
11import java.io.OutputStreamWriter;
12import java.net.Socket;
13import java.util.Arrays;
14import java.util.Scanner;
15import java.util.Stack;
16import javax.swing.SwingUtilities;
17
18
19import com.sun.jna.*;
20import com.sun.jna.platform.win32.Kernel32;
21import com.sun.jna.platform.win32.WinNT;
22
23import java.lang.reflect.Field;
24
25import org.apache.log4j.*;
26
27//import org.greenstone.gatherer.DebugStream;
28
29// Use this class to run a Java Process. It follows the good and safe practices at
30// http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html?page=2
31// to avoid blocking problems that can arise from a Process' input and output streams.
32
33// On Windows, Perl could launch processes as proper ProcessTrees: http://search.cpan.org/~gsar/libwin32-0.191/
34// Then killing the root process will kill child processes naturally.
35
36public class SafeProcess {
37 public static int DEBUG = 0;
38
39 public static final int STDERR = 0;
40 public static final int STDOUT = 1;
41 public static final int STDIN = 2;
42 // can't make this variable final and init in a static block, because it needs to use other SafeProcess static methods which rely on this in turn:
43 public static String WIN_KILL_CMD;
44
45 /**
46 * Boolean interruptible is used to mark any sections of blocking code that should not be interrupted
47 * with an InterruptedExceptions. At present only the cancelRunningProcess() attempts to do such a thing
48 * and avoids doing so when interruptible is false.
49 * Note that interruptible is also used as a lock, so remember to synchronize on it when using it!
50 */
51 public Boolean interruptible = Boolean.TRUE;
52
53 // charset for reading process stderr and stdout streams
54 //public static final String UTF8 = "UTF-8";
55
56 static Logger logger = Logger.getLogger(org.greenstone.util.SafeProcess.class.getName());
57
58 // input to SafeProcess and initialising it
59 private String command = null;
60 private String[] command_args = null;
61 private String[] envp = null;
62 private File dir = null;
63 private String inputStr = null;
64 private Process process = null;
65 private boolean forciblyTerminateProcess = false;
66
67 /** a ref to the thread in which the Process is being executed (the thread wherein Runtime.exec() is called) */
68 private Thread theProcessThread = null;
69
70 // output from running SafeProcess.runProcess()
71 private String outputStr = "";
72 private String errorStr = "";
73 private int exitValue = -1;
74 //private String charset = null;
75
76 // allow callers to process exceptions of the main process thread if they want
77 private ExceptionHandler exceptionHandler = null;
78 /** allow callers to implement hooks that get called during the main phases of the internal
79 * process' life cycle, such as before and after process.destroy() gets called
80 */
81 private MainProcessHandler mainHandler = null;
82
83 // whether std/err output should be split at new lines
84 private boolean splitStdOutputNewLines = false;
85 private boolean splitStdErrorNewLines = false;
86
87 // call one of these constructors
88
89 // cmd args version
90 public SafeProcess(String[] cmd_args)
91 {
92 command_args = cmd_args;
93 }
94
95 // cmd string version
96 public SafeProcess(String cmdStr)
97 {
98 command = cmdStr;
99 }
100
101 // cmd args with env version, launchDir can be null.
102 public SafeProcess(String[] cmd_args, String[] envparams, File launchDir)
103 {
104 command_args = cmd_args;
105 envp = envparams;
106 dir = launchDir;
107 }
108
109 // The important methods:
110 // to get the output from std err and std out streams after the process has been run
111 public String getStdOutput() { return outputStr; }
112 public String getStdError() { return errorStr; }
113 public int getExitValue() { return exitValue; }
114
115 //public void setStreamCharSet(String charset) { this.charset = charset; }
116
117 // set any string to send as input to the process spawned by SafeProcess
118 public void setInputString(String sendStr) {
119 inputStr = sendStr;
120 }
121
122 // register a SafeProcess ExceptionHandler whose gotException() method will
123 // get called for each exception encountered
124 public void setExceptionHandler(ExceptionHandler exception_handler) {
125 exceptionHandler = exception_handler;
126 }
127
128 /** to set a handler that will handle the main (SafeProcess) thread,
129 * implementing the hooks that will get called during the internal process' life cycle,
130 * such as before and after process.destroy() is called */
131 public void setMainHandler(MainProcessHandler handler) {
132 this.mainHandler = handler;
133 }
134
135 // set if you want the std output or err output to have \n at each newline read from the stream
136 public void setSplitStdOutputNewLines(boolean split) {
137 splitStdOutputNewLines = split;
138 }
139 public void setSplitStdErrorNewLines(boolean split) {
140 splitStdErrorNewLines = split;
141 }
142
143
144 /*
145 public boolean canInterrupt() {
146 boolean canInterrupt;
147 synchronized(interruptible) {
148 canInterrupt = interruptible.booleanValue();
149 }
150 return canInterrupt;
151 }
152 */
153
154
155 /**
156 * If calling this method from a GUI thread when the SafeProcess is in the uninterruptible
157 * phase of natural termination, then this method will return immediately before that phase
158 * has ended. To force the caller to wait until the natural termination phase has ended,
159 * call the other variant of this method with param forceWaitUntilInterruptible set to true:
160 * cancelRunningProcess(true).
161 * @return false if process has already terminated or if it was already terminating when
162 * cancel was called. In such cases no interrupt is sent.
163 * This method returns a boolean that you can call sentInterrupt.
164 */
165 public boolean cancelRunningProcess() {
166
167 boolean forceWaitUntilInterruptible = true;
168 // by default, event dispatch threads may not want to wait for any joins() taking
169 // place at the time of cancel to be completed.
170 // So don't wait until the SafeProcess becomes interruptible
171 return this.cancelRunningProcess(!forceWaitUntilInterruptible);
172 }
173
174 /**
175 * Call this method when you want to prematurely and safely terminate any process
176 * that SafeProcess may be running.
177 * You may want to implement the SafeProcess.MainHandler interface to write code
178 * for any hooks that will get called during the process' life cycle.
179 * @param forceWaitUntilInterruptible if set to true by a calling GUI thread, then this method
180 * won't return until the running process is interruptible, even if SafeProcess is in the phase
181 * of naturally terminating, upon which no interrupts will be sent to the SafeProcess
182 * thread anyway. The join() calls within SafeProcess.runProcess() are blocking calls and are
183 * therefore sensitive to InterruptedExceptions. But the join() calls are part of the cleanup
184 * phase and shouldn't be interrupted, and nothing thereafter can be interrupted anyway.
185 * This method tends to be called with the param set to false. In that case, if the SafeProcess
186 * is in an uninterruptible phase (as can then only happen during clean up of natural
187 * termination) then a calling GUI thread will just return immediately. Meaning, the GUI thread
188 * won't wait for the SafeProcess thread to finish cleaning up.
189 * @return false if process has already terminated or if it was already terminating when
190 * cancel was called. In such cases no interrupt is sent.
191 * This method returns a boolean that you can call sentInterrupt.
192 */
193 public synchronized boolean cancelRunningProcess(boolean forceWaitUntilInterruptible) {
194 // on interrupt:
195 // - forciblyTerminate will be changed to true if the interrupt came in when the process was
196 // still running (and so before the process' streams were being joined)
197 // - and forciblyTerminate will still remain false if the interrupt happens when the process'
198 // streams are being/about to be joined (hence after the process naturally terminated).
199 // So we don't touch the value of this.forciblyTerminate here.
200 // The value of forciblyTerminate determines whether Process.destroy() and its associated before
201 // and after handlers are called or not: we don't bother destroying the process if it came to
202 // a natural end.
203
204 // no process to interrupt, so we're done
205 if(this.process == null) {
206 log("@@@ No Java process to interrupt.");
207 return false;
208 }
209
210 boolean sentInterrupt = false;
211
212 // can't interrupt when SafeProcess is joining (cleanly terminating) worker threads
213 // have to wait until afterward
214 if (interruptible) {
215 // either way, we can now interrupt the thread that SafeProcess.runProcess() is running in
216 if(this.theProcessThread != null) { // we stored a ref to the main thread that's to be interrupted
217 this.theProcessThread.interrupt();
218 log("@@@ Successfully sent interrupt to process.");
219 sentInterrupt = true;
220 }
221 }
222 else { // wait for join()s to finish, if we've been asked to wait
223
224 // During and after joining(), there's no need to interrupt any more anyway: no calls
225 // subsequent to joins() block, so everything thereafter is insensitive to InterruptedExceptions
226 // and everything from the joins() onward are cleanup on natural process termination, so no
227 // interrupt is needed after the joins().
228 // Still, even if the caller is a GUI thread, they can decide if they want to wait until this
229 // method's end: until the SafeProcess becomes interruptible again
230
231 if(!forceWaitUntilInterruptible && SwingUtilities.isEventDispatchThread()) {
232 log("#### Event Dispatch thread, returning");
233 return false;
234 }
235
236 while(!interruptible) {
237
238 log("######### Waiting for process to become interruptible...");
239
240 // https://docs.oracle.com/javase/tutorial/essential/concurrency/guardmeth.html
241 // wait will release lock on this object, and regain it when loop condition interruptible is true
242 try {
243 this.wait(); // can't interrupt when SafeProcess is joining (cleanly terminating) worker threads, so wait
244 } catch(Exception e) {
245 log("@@@ Interrupted exception while waiting for SafeProcess' worker threads to finish joining on cancelling process");
246 }
247 }
248
249 // now the process is sure to have ended as the worker threads would have been joined
250 }
251
252 return sentInterrupt;
253 }
254
255
256 // In future, think of changing the method doRuntimeExec() over to using ProcessBuilder
257 // instead of Runtime.exec(). ProcessBuilder seems to have been introduced from Java 5.
258 // https://docs.oracle.com/javase/7/docs/api/java/lang/ProcessBuilder.html
259 // See also https://zeroturnaround.com/rebellabs/how-to-deal-with-subprocesses-in-java/
260 // which suggests using Apache Common Exec to launch processes and says what will be forthcoming in Java 9
261
262 private Process doRuntimeExec() throws IOException {
263 Process prcs = null;
264 Runtime rt = Runtime.getRuntime();
265
266 if(this.command != null) {
267 log("SafeProcess running: " + command);
268 prcs = rt.exec(this.command);
269 }
270 else { // at least command_args must be set now
271
272 // http://stackoverflow.com/questions/5283444/convert-array-of-strings-into-a-string-in-java
273 //log("SafeProcess running:" + Arrays.toString(command_args));
274 StringBuffer cmdDisplay = new StringBuffer();
275 for(int i = 0; i < command_args.length; i++) {
276 cmdDisplay.append(" ").append(command_args[i]);
277 }
278 log("SafeProcess running: [" + cmdDisplay + "]");
279 cmdDisplay = null; // let the GC have it
280
281
282 if(this.envp == null) {
283 prcs = rt.exec(this.command_args);
284 } else { // launch process using cmd str with env params
285
286 if(this.dir == null) {
287 //log("\twith: " + Arrays.toString(this.envp));
288 prcs = rt.exec(this.command_args, this.envp);
289 } else {
290 //log("\tfrom directory: " + this.dir);
291 //log("\twith: " + Arrays.toString(this.envp));
292 prcs = rt.exec(this.command_args, this.envp, this.dir);
293 }
294 }
295 }
296
297 this.theProcessThread = Thread.currentThread(); // store a ref to the thread wherein the Process is being run
298 return prcs;
299 }
300
301 // Copied from gli's gui/FormatConversionDialog.java
302 private int waitForWithStreams(SafeProcess.OutputStreamGobbler inputGobbler,
303 SafeProcess.InputStreamGobbler outputGobbler,
304 SafeProcess.InputStreamGobbler errorGobbler)
305 throws IOException, InterruptedException
306 {
307 // kick off the stream gobblers
308 inputGobbler.start();
309 errorGobbler.start();
310 outputGobbler.start();
311
312 try {
313 this.exitValue = process.waitFor(); // can throw an InterruptedException if process was cancelled/prematurely terminated
314 } catch(InterruptedException ie) {
315 log("*** Process interrupted (InterruptedException). Expected to be a Cancel operation.");
316 // don't print stacktrace: an interrupt here is not an error, it's expected to be a cancel action
317 if(exceptionHandler != null) {
318 exceptionHandler.gotException(ie);
319 }
320
321 // propagate interrupts to worker threads here
322 // unless the interrupt emanated from any of them in any join(),
323 // which will be caught by the calling method's own catch on InterruptedException.
324 // Only if the thread that SafeProcess runs in was interrupted
325 // should we propagate the interrupt to the worker threads.
326 // http://stackoverflow.com/questions/2126997/who-is-calling-the-java-thread-interrupt-method-if-im-not
327 // "I know that in JCiP it is mentioned that you should never interrupt threads you do not own"
328 // But SafeProcess owns the worker threads, so it has every right to interrupt them
329 // Also read http://stackoverflow.com/questions/13623445/future-cancel-method-is-not-working?noredirect=1&lq=1
330
331 // http://stackoverflow.com/questions/3976344/handling-interruptedexception-in-java
332 // http://stackoverflow.com/questions/4906799/why-invoke-thread-currentthread-interrupt-when-catch-any-interruptexception
333 // "Only code that implements a thread's interruption policy may swallow an interruption request. General-purpose task and library code should never swallow interruption requests."
334 // Does that mean that since this code implements this thread's interruption policy, it's ok
335 // to swallow the interrupt this time and not let it propagate by commenting out the next line?
336 //Thread.currentThread().interrupt(); // re-interrupt the thread
337
338 inputGobbler.interrupt();
339 errorGobbler.interrupt();
340 outputGobbler.interrupt();
341
342 // Since we have been cancelled (InterruptedException), or on any Exception, we need
343 // to forcibly terminate process eventually after the finally code first waits for each worker thread
344 // to die off. Don't set process=null until after we've forcibly terminated it if needs be.
345 this.forciblyTerminateProcess = true;
346
347 // even after the interrupts, we want to proceed to calling join() on all the worker threads
348 // in order to wait for each of them to die before attempting to destroy the process if it
349 // still hasn't terminated after all that.
350 } finally {
351
352 //log("Process exitValue: " + exitValue);
353 ///log("@@@@ Before join phase. Forcibly terminating: " + this.forciblyTerminateProcess);
354
355 // From the comments of
356 // http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html?page=2
357 // To avoid running into nondeterministic failures to get the process output
358 // if there's no waiting for the threads, call join() on each Thread (StreamGobbler) object.
359 // From Thread API: join() "Waits for this thread (the thread join() is invoked on) to die."
360
361 // Wait for each of the threads to die, before attempting to destroy the process
362 // Any of these can throw InterruptedExceptions too
363 // and will be processed by the calling function's catch on InterruptedException.
364
365
366 // Thread.joins() below are blocking calls, same as Process.waitFor(), and a cancel action could
367 // send an interrupt during any Join: the InterruptedException ensuing will then break out of the
368 // joins() section. We don't want that to happen: by the time the joins() start happening, the
369 // actual process has finished in some way (naturally terminated or interrupted), and nothing
370 // should interrupt the joins() (nor ideally any potential p.destroy after that).
371 // So we mark the join() section as an un-interruptible section, and make anyone who's seeking
372 // to interrupt just then first wait for this Thread (in which SafeProcess runs) to become
373 // interruptible again. Thos actually assumes anything interruptible can still happen thereafter
374 // when in reality, none of the subsequent actions after the joins() block. So they nothing
375 // thereafter, which is the cleanup phase, will actually respond to an InterruptedException.
376
377
378 if(this.mainHandler != null) {
379 // this method can unset forcible termination flag
380 // if the process had already naturally terminated by this stage:
381 this.forciblyTerminateProcess = mainHandler.beforeWaitingForStreamsToEnd(this.forciblyTerminateProcess);
382 }
383
384 ///log("@@@@ After beforeJoin Handler. Forcibly terminating: " + this.forciblyTerminateProcess);
385
386 // Anyone could interrupt/cancel during waitFor() above,
387 // but no one should interrupt while the worker threads come to a clean close,
388 // so make anyone wanting to cancel the process at this stage wait()
389 // until we're done with the join()s:
390 synchronized(interruptible) {
391 interruptible = Boolean.FALSE;
392 }
393 //Thread.sleep(5000); // Uncomment to test this uninterruptible section, also comment out block checking for
394 // EventDispatchThread in cancelRunningProcess() and 2 calls to progress.enableCancelJob() in DownloadJob.java
395 outputGobbler.join();
396 errorGobbler.join();
397 inputGobbler.join();
398
399 synchronized(interruptible) {
400 interruptible = Boolean.TRUE;
401 }
402
403 ///log("@@@@ Join phase done...");
404
405 // notify any of those waiting to interrupt this thread, that they may feel free to do so again
406 // https://docs.oracle.com/javase/tutorial/essential/concurrency/guardmeth.html
407 synchronized(this) {
408 this.notify();
409 }
410
411 // set the variables that the code which created a SafeProcess object may want to inspect
412 this.outputStr = outputGobbler.getOutput();
413 this.errorStr = errorGobbler.getOutput();
414
415 // call the after join()s hook
416 if(this.mainHandler != null) {
417 this.forciblyTerminateProcess = mainHandler.afterStreamsEnded(this.forciblyTerminateProcess);
418 }
419 }
420
421 // Don't return from finally, it's considered an abrupt completion and exceptions are lost, see
422 // http://stackoverflow.com/questions/18205493/can-we-use-return-in-finally-block
423 return this.exitValue;
424 }
425
426
427 public synchronized boolean processRunning() {
428 if(process == null) return false;
429 return SafeProcess.processRunning(this.process);
430 }
431
432 // Run a very basic process: with no reading from or writing to the Process' iostreams,
433 // this just execs the process and waits for it to return.
434 // Don't call this method but the zero-argument runProcess() instead if your process will
435 // output stuff to its stderr and stdout streams but you don't need to monitory these.
436 // Because, as per a comment in GLI's GS3ServerThread.java,
437 // in Java 6, it wil block if you don't handle a process' streams when the process is
438 // outputting something. (Java 7+ won't block if you don't bother to handle the output streams)
439 public int runBasicProcess() {
440 try {
441 this.forciblyTerminateProcess = true;
442
443 // 1. create the process
444 process = doRuntimeExec();
445 // 2. basic waitFor the process to finish
446 this.exitValue = process.waitFor();
447
448 // 3. if we managed to get here, the process naturally terminated (wasn't interrupted):
449 this.forciblyTerminateProcess = false;
450 } catch(IOException ioe) {
451
452 if(exceptionHandler != null) {
453 exceptionHandler.gotException(ioe);
454 } else {
455 log("IOException: " + ioe.getMessage(), ioe);
456 }
457 } catch(InterruptedException ie) {
458
459 if(exceptionHandler != null) {
460 exceptionHandler.gotException(ie);
461 } else { // Unexpected InterruptedException, so printstacktrace
462 log("Process InterruptedException: " + ie.getMessage(), ie);
463 }
464
465 Thread.currentThread().interrupt();
466 } finally {
467
468 cleanUp("SafeProcess.runBasicProcess");
469 }
470 return this.exitValue;
471 }
472
473 // Runs a process with default stream processing. Returns the exitValue
474 public int runProcess() {
475 return runProcess(null, null, null); // use default processing of all 3 of the process' iostreams
476 }
477
478 // Run a process with custom stream processing (any custom handlers passed in that are null
479 // will use the default stream processing).
480 // Returns the exitValue from running the Process
481 public int runProcess(CustomProcessHandler procInHandler,
482 CustomProcessHandler procOutHandler,
483 CustomProcessHandler procErrHandler)
484 {
485 SafeProcess.OutputStreamGobbler inputGobbler = null;
486 SafeProcess.InputStreamGobbler errorGobbler = null;
487 SafeProcess.InputStreamGobbler outputGobbler = null;
488
489 try {
490 this.forciblyTerminateProcess = false;
491
492 // 1. get the Process object
493 process = doRuntimeExec();
494
495
496 // 2. create the streamgobblers and set any specified handlers on them
497
498 // PROC INPUT STREAM
499 if(procInHandler == null) {
500 // send inputStr to process. The following constructor can handle inputStr being null
501 inputGobbler = // WriterToProcessInputStream
502 new SafeProcess.OutputStreamGobbler(process.getOutputStream(), this.inputStr);
503 } else { // user will do custom handling of process' InputStream
504 inputGobbler = new SafeProcess.OutputStreamGobbler(process.getOutputStream(), procInHandler);
505 }
506
507 // PROC ERR STREAM to monitor for any error messages or expected output in the process' stderr
508 if(procErrHandler == null) {
509 errorGobbler // ReaderFromProcessOutputStream
510 = new SafeProcess.InputStreamGobbler(process.getErrorStream(), this.splitStdErrorNewLines);
511 } else {
512 errorGobbler
513 = new SafeProcess.InputStreamGobbler(process.getErrorStream(), procErrHandler);
514 }
515
516 // PROC OUT STREAM to monitor for the expected std output line(s)
517 if(procOutHandler == null) {
518 outputGobbler
519 = new SafeProcess.InputStreamGobbler(process.getInputStream(), this.splitStdOutputNewLines);
520 } else {
521 outputGobbler
522 = new SafeProcess.InputStreamGobbler(process.getInputStream(), procOutHandler);
523 }
524
525
526 // 3. kick off the stream gobblers
527 this.exitValue = waitForWithStreams(inputGobbler, outputGobbler, errorGobbler);
528
529 } catch(IOException ioe) {
530 this.forciblyTerminateProcess = true;
531
532 if(exceptionHandler != null) {
533 exceptionHandler.gotException(ioe);
534 } else {
535 log("IOexception: " + ioe.getMessage(), ioe);
536 }
537 } catch(InterruptedException ie) { // caused during any of the gobblers.join() calls, this is unexpected so print stack trace
538 this.forciblyTerminateProcess = true;
539
540 if(exceptionHandler != null) {
541 exceptionHandler.gotException(ie);
542 log("@@@@ Unexpected InterruptedException when waiting for process stream gobblers to die");
543 } else {
544 log("*** Unexpected InterruptException when waiting for process stream gobblers to die: " + ie.getMessage(), ie);
545 }
546
547 // see comments in other runProcess()
548 Thread.currentThread().interrupt();
549
550 } finally {
551
552 cleanUp("SafeProcess.runProcess(3 params)");
553 }
554
555 return this.exitValue;
556 }
557
558 public int runProcess(LineByLineHandler outLineByLineHandler, LineByLineHandler errLineByLineHandler)
559 {
560 SafeProcess.OutputStreamGobbler inputGobbler = null;
561 SafeProcess.InputStreamGobbler errorGobbler = null;
562 SafeProcess.InputStreamGobbler outputGobbler = null;
563
564 try {
565 this.forciblyTerminateProcess = false;
566
567 // 1. get the Process object
568 process = doRuntimeExec();
569
570
571 // 2. create the streamgobblers and set any specified handlers on them
572
573 // PROC INPUT STREAM
574 // send inputStr to process. The following constructor can handle inputStr being null
575 inputGobbler = // WriterToProcessInputStream
576 new SafeProcess.OutputStreamGobbler(process.getOutputStream(), this.inputStr);
577
578 // PROC ERR STREAM to monitor for any error messages or expected output in the process' stderr
579 errorGobbler // ReaderFromProcessOutputStream
580 = new SafeProcess.InputStreamGobbler(process.getErrorStream(), splitStdErrorNewLines);
581 // PROC OUT STREAM to monitor for the expected std output line(s)
582 outputGobbler
583 = new SafeProcess.InputStreamGobbler(process.getInputStream(), splitStdOutputNewLines);
584
585
586 // 3. register line by line handlers, if any were set, for the process stderr and stdout streams
587 if(outLineByLineHandler != null) {
588 outputGobbler.setLineByLineHandler(outLineByLineHandler);
589 }
590 if(errLineByLineHandler != null) {
591 errorGobbler.setLineByLineHandler(errLineByLineHandler);
592 }
593
594
595 // 3. kick off the stream gobblers
596 this.exitValue = waitForWithStreams(inputGobbler, outputGobbler, errorGobbler);
597
598 } catch(IOException ioe) {
599 this.forciblyTerminateProcess = true;
600
601 if(exceptionHandler != null) {
602 exceptionHandler.gotException(ioe);
603 } else {
604 log("IOexception: " + ioe.getMessage(), ioe);
605 }
606 } catch(InterruptedException ie) { // caused during any of the gobblers.join() calls, this is unexpected so log it
607 this.forciblyTerminateProcess = true;
608
609 if(exceptionHandler != null) {
610 exceptionHandler.gotException(ie);
611 log("@@@@ Unexpected InterruptedException when waiting for process stream gobblers to die");
612 } else {
613 log("*** Unexpected InterruptException when waiting for process stream gobblers to die: " + ie.getMessage(), ie);
614 }
615 // We're not causing any interruptions that may occur when trying to stop the worker threads
616 // So resort to default behaviour in this catch?
617 // "On catching InterruptedException, re-interrupt the thread."
618 // This is just how InterruptedExceptions tend to be handled
619 // See also http://stackoverflow.com/questions/4906799/why-invoke-thread-currentthread-interrupt-when-catch-any-interruptexception
620 // and https://praveer09.github.io/technology/2015/12/06/understanding-thread-interruption-in-java/
621 Thread.currentThread().interrupt(); // re-interrupt the thread - which thread? Infinite loop?
622
623 } finally {
624
625 cleanUp("SafeProcess.runProcess(2 params)");
626 }
627
628 return this.exitValue;
629 }
630
631 private void cleanUp(String callingMethod) {
632
633 // Moved into here from GS2PerlConstructor and GShell.runLocal() which said
634 // "I need to somehow kill the child process. Unfortunately Thread.stop() and Process.destroy() both fail to do this. But now, thankx to the magic of Michaels 'close the stream suggestion', it works fine (no it doesn't!)"
635 // http://steveliles.github.io/invoking_processes_from_java.html
636 // http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html?page=2
637 // http://mark.koli.ch/leaky-pipes-remember-to-close-your-streams-when-using-javas-runtimegetruntimeexec
638
639 //String cmd = (this.command == null) ? Arrays.toString(this.command_args) : this.command;
640 //log("*** In finally of " + callingMethod + ": " + cmd);
641
642 // if we're forcibly terminating the process, call the before- and afterDestroy hooks
643 // besides actually destroying the process
644 if( this.forciblyTerminateProcess ) {
645 log("*** Going to call process.destroy from " + callingMethod);
646
647 if(mainHandler != null) mainHandler.beforeProcessDestroy();
648 boolean noNeedToDestroyIfOnLinux = true; // Interrupt handling suffices to cleanup process and subprocesses on Linux
649 SafeProcess.destroyProcess(process, noNeedToDestroyIfOnLinux); // see runProcess(2 args/3 args)
650 if(mainHandler != null) mainHandler.afterProcessDestroy();
651
652 log("*** Have called process.destroy from " + callingMethod);
653 }
654
655 process = null;
656 this.theProcessThread = null; // let the process thread ref go too
657 boolean wasForciblyTerminated = this.forciblyTerminateProcess;
658 this.forciblyTerminateProcess = false; // reset
659
660 if(mainHandler != null) mainHandler.doneCleanup(wasForciblyTerminated);
661 }
662
663/*
664
665 On Windows, p.destroy() terminates process p that Java launched,
666 but does not terminate any processes that p may have launched. Presumably since they didn't form a proper process tree.
667 https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/e3cb7532-87f6-4ae3-9d80-a3afc8b9d437/how-to-kill-a-process-tree-in-cc-on-windows-platform?forum=vclanguage
668 https://msdn.microsoft.com/en-us/library/windows/desktop/ms684161(v=vs.85).aspx
669
670 Searching for: "forcibly terminate external process launched by Java on Windows"
671 Not possible: stackoverflow.com/questions/1835885/send-ctrl-c-to-process-open-by-java
672 But can use taskkill or tskill or wmic commands to terminate a process by processID
673 stackoverflow.com/questions/912889/how-to-send-interrupt-key-sequence-to-a-java-process
674 Taskkill command can kill by Image Name, such as all running perl, e.g. taskkill /f /im perl.exe
675 But what if we kill perl instances not launched by GS?
676 /f Specifies to forcefully terminate the process(es). We need this flag switched on to kill childprocesses.
677 /t Terminates the specified process and any child processes which were started by it.
678 /t didn't work to terminate subprocesses. Maybe since the process wasn't launched as
679 a properly constructed processtree.
680 /im is the image name (the name of the program), see Image Name column in Win Task Manager.
681
682 We don't want to kill all perl running processes.
683 Another option is to use wmic, available since Windows XP, to kill a process based on its command
684 which we sort of know (SafeProcess.command) and which can be seen in TaskManager under the
685 "Command Line" column of the Processes tab.
686 https://superuser.com/questions/52159/kill-a-process-with-a-specific-command-line-from-command-line
687 The following works kill any Command Line that matches -site localsite lucene-jdbm-demo
688 C:>wmic PATH win32_process Where "CommandLine like '%-site%localsite%%lucene-jdbm-demo%'" Call Terminate
689 "WMIC Wildcard Search using 'like' and %"
690 https://codeslammer.wordpress.com/2009/02/21/wmic-wildcard-search-using-like-and/
691 However, we're not even guaranteed that every perl command GS launches will contain the collection name
692 Nor do we want to kill all perl processes that GS launches with bin\windows\perl\bin\perl, though this works:
693 wmic PATH win32_process Where "CommandLine like '%bin%windows%perl%bin%perl%'" Call Terminate
694 The above could kill GS perl processes we don't intend to terminate, as they're not spawned by the particular
695 Process we're trying to terminate from the root down.
696
697 Solution: We can use taskkill or the longstanding tskill or wmic to kill a process by ID. Since we can
698 kill an external process that SafeProcess launched OK, and only have trouble killing any child processes
699 it launched, we need to know the pids of the child processes.
700
701 We can use Windows' wmic to discover the childpids of a process whose id we know.
702 And we can use JNA to get the process ID of the external process that SafeProcess launched.
703
704 To find the processID of the process launched by SafeProcess,
705 need to use Java Native Access (JNA) jars, available jna.jar and jna-platform.jar.
706 http://stackoverflow.com/questions/4750470/how-to-get-pid-of-process-ive-just-started-within-java-program
707 http://stackoverflow.com/questions/35842/how-can-a-java-program-get-its-own-process-id
708 http://www.golesny.de/p/code/javagetpid
709 https://github.com/java-native-access/jna/blob/master/www/GettingStarted.md
710 We're using JNA v 4.1.0, https://mvnrepository.com/artifact/net.java.dev.jna/jna
711
712 WMIC can show us a list of parent process id and process id of running processes, and then we can
713 kill those child processes with a specific process id.
714 https://superuser.com/questions/851692/track-which-program-launches-a-certain-process
715 http://stackoverflow.com/questions/7486717/finding-parent-process-id-on-windows
716 WMIC can get us the pids of all childprocesses launched by parent process denoted by parent pid.
717 And vice versa:
718 if you know the parent pid and want to know all the pids of the child processes spawned:
719 wmic process where (parentprocessid=596) get processid
720 if you know a child process id and want to know the parent's id:
721 wmic process where (processid=180) get parentprocessid
722
723 The above is the current solution.
724
725 Eventually, instead of running a windows command to kill the process ourselves, consider changing over to use
726 https://github.com/flapdoodle-oss/de.flapdoodle.embed.process/blob/master/src/main/java/de/flapdoodle/embed/process/runtime/Processes.java
727 (works with Apache license, http://www.apache.org/licenses/LICENSE-2.0)
728 This is a Java class that uses JNA to terminate processes. It also has the getProcessID() method.
729
730 Linux ps equivalent on Windows is "tasklist", see
731 http://stackoverflow.com/questions/4750470/how-to-get-pid-of-process-ive-just-started-within-java-program
732
733*/
734
735// http://stackoverflow.com/questions/4750470/how-to-get-pid-of-process-ive-just-started-within-java-program
736// Uses Java Native Access, JNA
737public static long getProcessID(Process p)
738{
739 long pid = -1;
740 try {
741 //for windows
742 if (p.getClass().getName().equals("java.lang.Win32Process") ||
743 p.getClass().getName().equals("java.lang.ProcessImpl"))
744 {
745 Field f = p.getClass().getDeclaredField("handle");
746 f.setAccessible(true);
747 long handl = f.getLong(p);
748 Kernel32 kernel = Kernel32.INSTANCE;
749 WinNT.HANDLE hand = new WinNT.HANDLE();
750 hand.setPointer(Pointer.createConstant(handl));
751 pid = kernel.GetProcessId(hand);
752 f.setAccessible(false);
753 }
754 //for unix based operating systems
755 else if (p.getClass().getName().equals("java.lang.UNIXProcess"))
756 {
757 Field f = p.getClass().getDeclaredField("pid");
758 f.setAccessible(true);
759 pid = f.getLong(p);
760 f.setAccessible(false);
761 }
762
763 } catch(Exception ex) {
764 log("SafeProcess.getProcessID(): Exception when attempting to get process ID for process " + ex.getMessage(), ex);
765 pid = -1;
766 }
767 return pid;
768}
769
770
771// Can't artificially send Ctrl-C: stackoverflow.com/questions/1835885/send-ctrl-c-to-process-open-by-java
772// (Taskkill command can kill all running perl. But what if we kill perl instances not launched by GS?)
773// stackoverflow.com/questions/912889/how-to-send-interrupt-key-sequence-to-a-java-process
774// Searching for: "forcibly terminate external process launched by Java on Windows"
775static void killWinProcessWithID(long processID) {
776
777 String cmd = SafeProcess.getWinProcessKillCmd(processID);
778 if (cmd == null) return;
779
780 try {
781 log("\tAttempting to terminate Win subprocess with pid: " + processID);
782 SafeProcess proc = new SafeProcess(cmd);
783 int exitValue = proc.runProcess(); // no IOstreams for Taskkill, but for "wmic process pid delete"
784 // there is output that needs flushing, so don't use runBasicProcess()
785
786 } catch(Exception e) {
787 log("@@@ Exception attempting to stop perl " + e.getMessage(), e);
788 }
789}
790
791// Kill signals, their names and numerical equivalents: http://www.faqs.org/qa/qa-831.html
792// https://stackoverflow.com/questions/8533377/why-child-process-still-alive-after-parent-process-was-killed-in-linux
793// Works on Linux but not Mac when build scripts run from GLI: kill -TERM -pid
794// Works on Macs but not Linux: pkill -TERM -P pid
795// More reading:
796// https://superuser.com/questions/343031/sigterm-with-a-keyboard-shortcut
797// Ctrl-C sends a SIGNINT, not SIGTERM or SIGKILL. And on Ctrl-C, "the signal is sent to the foreground *process group*."
798// https://linux.die.net/man/1/kill (manual)
799// https://unix.stackexchange.com/questions/117227/why-pidof-and-pgrep-are-behaving-differently
800// https://unix.stackexchange.com/questions/67635/elegantly-get-list-of-children-processes
801// https://stackoverflow.com/questions/994033/mac-os-x-quickest-way-to-kill-quit-an-entire-process-tree-from-within-a-cocoa-a
802// https://unix.stackexchange.com/questions/132224/is-it-possible-to-get-process-group-id-from-proc
803// https://unix.stackexchange.com/questions/99112/default-exit-code-when-process-is-terminated
804
805/**
806 * On Unix, will kill the process denoted by processID and any subprocesses this launched. Tested on a Mac, where this is used.
807 * @param force if true will send the -KILL (-9) signal, which may result in abrupt termination without cleanup
808 * if false, will send the -TERM (-15) signal, which will allow cleanup before termination. Sending a SIGTERM is preferred.
809 * @param killEntireTree if false, will terminate only the process denoted by processID, otherwise all descendants/subprocesses too.
810 * @return true if running the kill process returned an exit value of 0 or if it had already been terminated
811*/
812static boolean killUnixProcessWithID(long processID, boolean force, boolean killEntireTree) {
813
814 String signal = force ? "KILL" : "TERM"; // kill -KILL (kill -9) vs preferred kill -TERM (kill -15)
815 String cmd;
816 if(killEntireTree) { // kill the process denoted by processID and any subprocesses this launched
817
818 if(Misc.isMac()) {
819 // this cmd works on Mac (tested Snow Leopard), but on Linux this cmd only terminates toplevel process
820 // when doing full-import, and doesn't always terminate subprocesses when doing full-buildcol.pl
821 cmd = "pkill -"+signal + " -P " + processID; // e.g. "pkill -TERM -P pid"
822 }
823 else { // other unix
824 // this cmd works on linux, not recognised on Mac (tested Snow Leopard):
825 cmd = "kill -"+signal + " -"+processID; // e.g. "kill -TERM -pid"
826 // note the hyphen before pid to terminate subprocesses too
827 }
828
829 } else { // kill only the process represented by the processID.
830 cmd = "kill -"+signal + " " + processID; // e.g. "kill -TERM pid"
831 }
832
833 SafeProcess proc = new SafeProcess(cmd);
834 int exitValue = proc.runProcess();
835
836
837 if(exitValue == 0) {
838 if(force) {
839 log("@@@ Successfully sent SIGKILL to unix process tree rooted at " + processID);
840 } else {
841 log("@@@ Successfully sent SIGTERM to unix process tree rooted at " + processID);
842 }
843 return true;
844 } else if(exitValue == 1 && proc.getStdOutput().trim().equals("") && proc.getStdError().trim().equals("")) {
845 // https://stackoverflow.com/questions/28332888/return-value-of-kill
846 // "kill returns an exit code of 0 (true) if the process still existed it and was killed.
847 // kill returns an exit code of 1 (false) if the kill failed, probably because the process was no longer running."
848 // On Linux, interrupting the process and its worker threads and closing resources already successfully terminates
849 // the process and its subprocesses (don't need to call this method at all to terminate the processes: the processes
850 // aren't running when we get to this method)
851 log("@@@ Sending termination signal returned exit value 1. On unix this can happen when the process has already been terminated.");
852 return true;
853 } else {
854 log("@@@ Not able to successfully terminate process. Got exitvalue: " + exitValue);
855 log("@@@ Got output: |" + proc.getStdOutput() + "|");
856 log("@@@ Got err output: |" + proc.getStdError() + "|");
857 // caller can try again with kill -KILL, by setting force parameter to true
858 return false;
859 }
860}
861
862public static void destroyProcess(Process p) {
863 // A cancel action results in an interruption to the process thread, which in turn interrupts
864 // the SafeProcess' worker threads, all which clean up after themselves.
865 // On linux, this suffices to cleanly terminate a Process and any subprocesses that may have launched
866 // so we don't need to do extra work in such a case. But the interrupts happen only when SafeProcess calls
867 // destroyProcess() on the Process it was running internally, and not if anyone else tries to end a
868 // Process by calling SafeProcess.destroyProcess(p). In such cases, the Process needs to be actively terminated:
869 boolean canSkipExtraWorkIfLinux = true;
870 SafeProcess.destroyProcess(p, !canSkipExtraWorkIfLinux);
871}
872
873// On linux, the SafeProcess code handling an Interruption suffices to successfully and cleanly terminate
874// the process and any subprocesses launched by p as well (and not even an extra p.destroy() is needed).
875// On Windows, and Mac too, we need to do more work, since otherwise processes launched by p remain
876// around executing until they naturally terminate.
877// e.g. full-import.pl may be terminated with p.destroy(), but it launches import.pl which is left running until it naturally terminates.
878private static void destroyProcess(Process p, boolean canSkipExtraWorkIfLinux) {
879 log("### in SafeProcess.destroyProcess(Process p)");
880
881 // If it isn't windows, process.destroy() terminates any child processes too
882 if(Misc.isWindows()) {
883
884 if(!SafeProcess.isAvailable("wmic")) {
885 log("wmic, used to kill subprocesses, is not available. Unable to terminate subprocesses...");
886 log("Kill them manually from the TaskManager or they will proceed to run to termination");
887
888 // At least we can get rid of the top level process we launched
889 p.destroy();
890 return;
891 }
892
893 // get the process id of the process we launched,
894 // so we can use it to find the pids of any subprocesses it launched in order to terminate those too.
895
896 long processID = SafeProcess.getProcessID(p);
897 if(processID == -1) { // the process doesn't exist or no longer exists (terminated naturally?)
898 p.destroy(); // minimum step, do this anyway, at worst there's no process and this won't have any effect
899 } else {
900 log("Attempting to terminate sub processes of Windows process with pid " + processID);
901 terminateSubProcessesRecursively(processID, p);
902 }
903 return;
904
905 }
906 else { // linux or mac
907
908 // if we're on linux and would have already terminated by now (in which case canSkipExtraWorkForLinux would be true),
909 // then there's nothing much left to do. This would only be the case if SafeProcess is calling this method on its
910 // internal process, since it would have successfully cleaned up on Interruption and there would be no process left running
911 if(!Misc.isMac() && canSkipExtraWorkIfLinux) {
912 log("@@@ Linux: Cancelling a SafeProcess instance does not require any complicated system destroy operation");
913 p.destroy(); // vestigial: this will have no effect if the process had already terminated, which is the case in this block
914 return;
915 }
916 // else we're on a Mac or an external caller (not SafeProcess) has requested explicit termination on Linux
917
918 long pid = SafeProcess.getProcessID(p);
919 /*
920 // On Macs (all Unix?) can't get the child processes of a process once it's been destroyed
921 macTerminateSubProcessesRecursively(pid, p);
922 */
923
924 if(pid == -1) {
925 p.destroy(); // at minimum. Will have no effect if the process had already terminated
926 } else {
927 boolean forceKill = true;
928 boolean killEntireProcessTree = true;
929
930 if(!killUnixProcessWithID(pid, !forceKill, killEntireProcessTree)) { // send sig TERM (kill -15 or kill -TERM)
931 killUnixProcessWithID(pid, forceKill, killEntireProcessTree); // send sig KILL (kill -9 or kill -KILL)
932 }
933 }
934
935 return;
936 }
937}
938
939
940// UNUSED and INCOMPLETE METHOD
941// But if this method is needed, then need to parse childpids printed by "pgrep -P pid" and write recursive step
942// The childpids are probably listed one per line, see https://unix.stackexchange.com/questions/117227/why-pidof-and-pgrep-are-behaving-differently
943private static void macTerminateSubProcessesRecursively(long parent_pid, Process p) { //boolean isTopLevelProcess) {
944 log("@@@ Attempting to terminate mac process recursively");
945
946 // https://unix.stackexchange.com/questions/67635/elegantly-get-list-of-children-processes
947 SafeProcess proc = new SafeProcess("pgrep -P "+parent_pid);
948 int exitValue = proc.runProcess();
949 String stdOutput = proc.getStdOutput();
950 String stdErrOutput = proc.getStdError();
951
952 // now we have the child processes, can terminate the parent process
953 if(p != null) { // top level process, can just be terminated the java way with p.destroy()
954 p.destroy();
955 } else {
956 boolean forceKill = true;
957 boolean killSubprocesses = true;
958 // get rid of process denoted by the current pid (but not killing subprocesses it may have launched,
959 // since we'll deal with them recursively)
960 if(!SafeProcess.killUnixProcessWithID(parent_pid, !forceKill, !killSubprocesses)) { // send kill -TERM, kill -15
961 SafeProcess.killUnixProcessWithID(parent_pid, forceKill, !killSubprocesses); // send kill -9, kill -KILL
962 }
963 }
964
965 /*
966 // get rid of any process with current pid
967 if(!isTopLevelProcess && !SafeProcess.killUnixProcessWithID(parent_pid, false)) { // send kill -TERM, kill -15
968 SafeProcess.killUnixProcessWithID(parent_pid, true); // send kill -9, kill -KILL
969 }
970 */
971
972 if(stdOutput.trim().equals("") && stdErrOutput.trim().equals("") && exitValue == 1) {
973 log("No child processes");
974 // we're done
975 return;
976 } else {
977 log("Got childpids on STDOUT: " + stdOutput);
978 log("Got childpids on STDERR: " + stdErrOutput);
979 }
980}
981
982// Helper function. Only for Windows.
983// Counterintuitively, we're be killing all parent processess and then all child procs and all their descendants
984// as soon as we discover any further process each (sub)process has launched. The parent processes are killed
985// first in each case for 2 reasons:
986// 1. on Windows, killing the parent process leaves the child running as an orphan anyway, so killing the
987// parent is an independent action, the child process is not dependent on the parent;
988// 2. Killing a parent process prevents it from launching further processes while we're killing off each child process
989private static void terminateSubProcessesRecursively(long parent_pid, Process p) {
990
991 // Use Windows wmic to find the pids of any sub processes launched by the process denoted by parent_pid
992 SafeProcess proc = new SafeProcess("wmic process where (parentprocessid="+parent_pid+") get processid");
993 proc.setSplitStdOutputNewLines(true); // since this is windows, splits lines by \r\n
994 int exitValue = proc.runProcess(); // exitValue (%ERRORLEVEL%) is 0 either way.
995 //log("@@@@ Return value from proc: " + exitValue);
996
997 // need output from both stdout and stderr: stderr will say there are no pids, stdout will contain pids
998 String stdOutput = proc.getStdOutput();
999 String stdErrOutput = proc.getStdError();
1000
1001
1002 // Now we know the pids of the immediate subprocesses, we can get rid of the parent process
1003 // We know the children remain running: since the whole problem on Windows is that these
1004 // child processes remain running as orphans after the parent is forcibly terminated.
1005 if(p != null) { // we're the top level process, terminate the java way
1006 p.destroy();
1007 } else { // terminate windows way
1008 SafeProcess.killWinProcessWithID(parent_pid); // get rid of process with current pid
1009 }
1010
1011 // parse the output to get the sub processes' pids
1012 // Output looks like:
1013 // ProcessId
1014 // 6040
1015 // 180
1016 // 4948
1017 // 1084
1018 // 6384
1019 // If no children, then STDERR output starts with the following, possibly succeeded by empty lines:
1020 // No Instance(s) Available.
1021
1022 // base step of the recursion
1023 if(stdErrOutput.indexOf("No Instance(s) Available.") != -1) {
1024 //log("@@@@ Got output on stderr: " + stdErrOutput);
1025 // No further child processes. And we already terminated the parent process, so we're done
1026 return;
1027 } else {
1028 //log("@@@@ Got output on stdout:\n" + stdOutput);
1029
1030 // http://stackoverflow.com/questions/691184/scanner-vs-stringtokenizer-vs-string-split
1031
1032 // find all childprocesses for that pid and terminate them too:
1033 Stack<Long> subprocs = new Stack<Long>();
1034 Scanner sc = new Scanner(stdOutput);
1035 while (sc.hasNext()) {
1036 if(!sc.hasNextLong()) {
1037 sc.next(); // discard the current token since it's not a Long
1038 } else {
1039 long child_pid = sc.nextLong();
1040 subprocs.push(new Long(child_pid));
1041 }
1042 }
1043 sc.close();
1044
1045 // recursion step if subprocs is not empty (but if it is empty, then it's another base step)
1046 if(!subprocs.empty()) {
1047 long child_pid = subprocs.pop().longValue();
1048 terminateSubProcessesRecursively(child_pid, null);
1049 }
1050 }
1051}
1052
1053// This method should only be called on a Windows OS
1054private static String getWinProcessKillCmd(Long processID) {
1055 // check if we first need to init WIN_KILL_CMD. We do this only once, but can't do it in a static codeblock
1056 // because of a cyclical dependency regarding this during static initialization
1057
1058 if(WIN_KILL_CMD == null) {
1059 if(SafeProcess.isAvailable("wmic")) {
1060 // https://isc.sans.edu/diary/Windows+Command-Line+Kung+Fu+with+WMIC/1229
1061 WIN_KILL_CMD = "wmic process _PROCID_ delete"; // like "kill -9" on Windows
1062 }
1063 else if(SafeProcess.isAvailable("taskkill")) { // check if we have taskkill or else use the longstanding tskill
1064
1065 WIN_KILL_CMD = "taskkill /f /t /PID _PROCID_"; // need to forcefully /f terminate the process
1066 // /t "Terminates the specified process and any child processes which were started by it."
1067 // But despite the /T flag, the above doesn't kill subprocesses.
1068 }
1069 else { //if(SafeProcess.isAvailable("tskill")) { can't check availability since "which tskill" doesn't ever succeed
1070 WIN_KILL_CMD = "tskill _PROCID_"; // https://ss64.com/nt/tskill.html
1071 }
1072 }
1073
1074 if(WIN_KILL_CMD == null) { // can happen if none of the above cmds were available
1075 return null;
1076 }
1077 return WIN_KILL_CMD.replace( "_PROCID_", Long.toString(processID) );
1078}
1079
1080
1081// Run `which` on a program to find out if it is available. which.exe is included in winbin.
1082// On Windows, can use where or which. GLI's file/FileAssociationManager.java used which, so we stick to the same.
1083// where is not part of winbin. where is a system command on windows, but only since 2003, https://ss64.com/nt/where.html
1084// There is no `where` on Linux/Mac, must use which for them.
1085// On windows, "which tskill" fails (and "where tskill" works), but "which" succeeds on taskkill|wmic|browser names.
1086public static boolean isAvailable(String program) {
1087 try {
1088 // On linux `which bla` does nothing, prompt is returned; on Windows, it prints "which: no bla in"
1089 // `which grep` returns a line of output with the path to grep. On windows too, the location of the program is printed
1090 SafeProcess prcs = new SafeProcess("which " + program);
1091 prcs.runProcess();
1092 String output = prcs.getStdOutput().trim();
1093 ///System.err.println("*** 'which " + program + "' returned: |" + output + "|");
1094 if(output.equals("")) {
1095 return false;
1096 } else if(output.indexOf("no "+program) !=-1) { // from GS3's org.greenstone.util.BrowserLauncher.java's isAvailable(program)
1097 log("@@@ SafeProcess.isAvailable(): " + program + "is not available");
1098 return false;
1099 }
1100 //System.err.println("*** 'which " + program + "' returned: " + output);
1101 return true;
1102 } catch (Exception exc) {
1103 return false;
1104 }
1105}
1106
1107// Google Java external process destroy kill subprocesses
1108// https://zeroturnaround.com/rebellabs/how-to-deal-with-subprocesses-in-java/
1109
1110//******************** Inner class and interface definitions ********************//
1111// Static inner classes can be instantiated without having to instantiate an object of the outer class first
1112
1113// Can have public static interfaces too,
1114// see http://stackoverflow.com/questions/71625/why-would-a-static-nested-interface-be-used-in-java
1115// Implementors need to take care that the implementations are thread safe
1116// http://stackoverflow.com/questions/14520814/why-synchronized-method-is-not-included-in-interface
1117public static interface ExceptionHandler {
1118
1119 /**
1120 * Called whenever an exception occurs during the execution of the main thread of SafeProcess
1121 * (the thread in which the Process is run).
1122 * Since this method can't be declared as synchronized in this interface method declaration,
1123 * when implementing ExceptionHandler.gotException(), if it manipulates anything that's
1124 * not threadsafe, declare gotException() as a synchronized method to ensure thread safety
1125 */
1126 public void gotException(Exception e);
1127}
1128
1129/** On interrupting (cancelling) a process,
1130 * if the class that uses SafeProcess wants to do special handling
1131 * either before and after join() is called on all the worker threads,
1132 * or, only on forcible termination, before and after process.destroy() is to be called,
1133 * then that class can implement this MainProcessHandler interface
1134 */
1135public static interface MainProcessHandler {
1136 /**
1137 * Called before the streamgobbler join()s.
1138 * If not overriding, the default implementation should be:
1139 * public boolean beforeWaitingForStreamsToEnd(boolean forciblyTerminating) { return forciblyTerminating; }
1140 * When overriding:
1141 * @param forciblyTerminating is true if currently it's been decided that the process needs to be
1142 * forcibly terminated. Return false if you don't want it to be. For a basic implementation,
1143 * return the parameter.
1144 * @return true if the process is still running and therefore still needs to be destroyed, or if
1145 * you can't determine whether it's still running or not. Process.destroy() will then be called.
1146 * @return false if the process has already naturally terminated by this stage. Process.destroy()
1147 * won't be called, and neither will the before- and after- processDestroy methods of this class.
1148 */
1149 public boolean beforeWaitingForStreamsToEnd(boolean forciblyTerminating);
1150 /**
1151 * Called after the streamgobbler join()s have finished.
1152 * If not overriding, the default implementation should be:
1153 * public boolean afterStreamsEnded(boolean forciblyTerminating) { return forciblyTerminating; }
1154 * When overriding:
1155 * @param forciblyTerminating is true if currently it's been decided that the process needs to be
1156 * forcibly terminated. Return false if you don't want it to be. For a basic implementation,
1157 * return the parameter (usual case).
1158 * @return true if the process is still running and therefore still needs to be destroyed, or if
1159 * can't determine whether it's still running or not. Process.destroy() will then be called.
1160 * @return false if the process has already naturally terminated by this stage. Process.destroy()
1161 * won't be called, and neither will the before- and after- processDestroy methods of this class.
1162 */
1163 public boolean afterStreamsEnded(boolean forciblyTerminating);
1164 /**
1165 * called after join()s and before process.destroy()/destroyProcess(Process), iff forciblyTerminating
1166 */
1167 public void beforeProcessDestroy();
1168 /**
1169 * Called after process.destroy()/destroyProcess(Process), iff forciblyTerminating
1170 */
1171 public void afterProcessDestroy();
1172
1173 /**
1174 * Always called after process ended: whether it got destroyed or not
1175 */
1176 public void doneCleanup(boolean wasForciblyTerminated);
1177}
1178
1179// Write your own run() body for any StreamGobbler. You need to create an instance of a class
1180// extending CustomProcessHandler for EACH IOSTREAM of the process that you want to handle.
1181// Do not create a single CustomProcessHandler instance and reuse it for all three streams,
1182// i.e. don't call SafeProcess' runProcess(x, x, x); It should be runProcess(x, y, z).
1183// Make sure your implementation is threadsafe if you're sharing immutable objects between the threaded streams
1184// example implementation is in the GS2PerlConstructor.SynchronizedProcessHandler class.
1185// CustomProcessHandler is made an abstract class instead of an interface to force classes that want
1186// to use a CustomProcessHandler to create a separate class that extends CustomProcessHandler, rather than
1187// that the classes that wish to use it "implementing" the CustomProcessHandler interface itself: the
1188// CustomProcessHandler.run() method may then be called in the major thread from which the Process is being
1189// executed, rather than from the individual threads that deal with each iostream of the Process.
1190public static abstract class CustomProcessHandler {
1191
1192 protected final int source;
1193
1194 protected CustomProcessHandler(int src) {
1195 this.source = src; // STDERR or STDOUT or STDIN
1196 }
1197
1198 public String getThreadNamePrefix() {
1199 return SafeProcess.streamToString(this.source);
1200 }
1201
1202 public abstract void run(Closeable stream); //InputStream or OutputStream
1203}
1204
1205// When using the default stream processing to read from a process' stdout or stderr stream, you can
1206// create a class extending LineByLineHandler for the process' err stream and one for its output stream
1207// to do something on a line by line basis, such as sending the line to a log
1208public static abstract class LineByLineHandler {
1209 protected final int source;
1210
1211 protected LineByLineHandler(int src) {
1212 this.source = src; // STDERR or STDOUT
1213 }
1214
1215 public String getThreadNamePrefix() {
1216 return SafeProcess.streamToString(this.source);
1217 }
1218
1219 public abstract void gotLine(String line); // first non-null line
1220 public abstract void gotException(Exception e); // for when an exception occurs instead of getting a line
1221}
1222
1223
1224//**************** StreamGobbler Inner class definitions (stream gobblers copied from GLI) **********//
1225
1226// http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html?page=2
1227// This class is used in FormatConversionDialog to properly read from the stdout and stderr
1228// streams of a Process, Process.getInputStream() and Process.getErrorSream()
1229public static class InputStreamGobbler extends Thread
1230{
1231 private InputStream is = null;
1232 private StringBuffer outputstr = new StringBuffer();
1233 private boolean split_newlines = false;
1234 private CustomProcessHandler customHandler = null;
1235 private LineByLineHandler lineByLineHandler = null;
1236
1237 protected InputStreamGobbler() {
1238 super("InputStreamGobbler");
1239 }
1240
1241 public InputStreamGobbler(InputStream is)
1242 {
1243 this(); // sets thread name
1244 this.is = is;
1245 this.split_newlines = false;
1246 }
1247
1248 public InputStreamGobbler(InputStream is, boolean split_newlines)
1249 {
1250 this(); // sets thread name
1251 this.is = is;
1252 this.split_newlines = split_newlines;
1253
1254 }
1255
1256 public InputStreamGobbler(InputStream is, CustomProcessHandler customHandler)
1257 {
1258 this(); // thread name
1259 this.is = is;
1260 this.customHandler = customHandler;
1261 this.adjustThreadName(customHandler.getThreadNamePrefix());
1262 }
1263
1264
1265 private void adjustThreadName(String prefix) {
1266 this.setName(prefix + this.getName());
1267 }
1268
1269 public void setLineByLineHandler(LineByLineHandler lblHandler) {
1270 this.lineByLineHandler = lblHandler;
1271 this.adjustThreadName(lblHandler.getThreadNamePrefix());
1272 }
1273
1274 // default run() behaviour
1275 public void runDefault()
1276 {
1277 BufferedReader br = null;
1278 try {
1279 br = new BufferedReader(new InputStreamReader(is, "UTF-8"));
1280 String line=null;
1281 while ( !this.isInterrupted() && (line = br.readLine()) != null ) {
1282
1283 //log("@@@ GOT LINE: " + line);
1284 outputstr.append(line);
1285 if(split_newlines) {
1286 outputstr.append(Misc.NEWLINE); // "\n" is system dependent (Win must be "\r\n")
1287 }
1288
1289 if(lineByLineHandler != null) { // let handler deal with newlines
1290 lineByLineHandler.gotLine(line);
1291 }
1292 }
1293
1294 } catch (IOException ioe) {
1295 if(lineByLineHandler != null) {
1296 lineByLineHandler.gotException(ioe);
1297 } else {
1298 log("Exception when reading process stream with " + this.getName() + ": ", ioe);
1299 }
1300 } finally {
1301 if(this.isInterrupted()) {
1302 log("@@@ Successfully interrupted " + this.getName() + ".");
1303 }
1304 SafeProcess.closeResource(br);
1305 }
1306 }
1307
1308 public void runCustom() {
1309 this.customHandler.run(is);
1310 }
1311
1312 public void run() {
1313 if(this.customHandler == null) {
1314 runDefault();
1315 } else {
1316 runCustom();
1317 }
1318 }
1319
1320 public String getOutput() {
1321 return outputstr.toString(); // implicit toString() call anyway. //return outputstr;
1322 }
1323} // end static inner class InnerStreamGobbler
1324
1325
1326// http://www.javaworld.com/article/2071275/core-java/when-runtime-exec---won-t.html?page=2
1327// This class is used in FormatConversionDialog to properly write to the inputstream of a Process
1328// Process.getOutputStream()
1329public static class OutputStreamGobbler extends Thread
1330{
1331 private OutputStream os = null;
1332 private String inputstr = "";
1333 private CustomProcessHandler customHandler = null;
1334
1335 protected OutputStreamGobbler() {
1336 super("stdinOutputStreamGobbler"); // thread name
1337 }
1338
1339 public OutputStreamGobbler(OutputStream os) {
1340 this(); // set thread name
1341 this.os = os;
1342 }
1343
1344 public OutputStreamGobbler(OutputStream os, String inputstr)
1345 {
1346 this(); // set thread name
1347 this.os = os;
1348 this.inputstr = inputstr;
1349 }
1350
1351 public OutputStreamGobbler(OutputStream os, CustomProcessHandler customHandler) {
1352 this(); // set thread name
1353 this.os = os;
1354 this.customHandler = customHandler;
1355 }
1356
1357 // default run() behaviour
1358 public void runDefault() {
1359
1360 if (inputstr == null) {
1361 return;
1362 }
1363
1364 // also quit if the process was interrupted before we could send anything to its stdin
1365 if(this.isInterrupted()) {
1366 log(this.getName() + " thread was interrupted.");
1367 return;
1368 }
1369
1370 BufferedWriter osw = null;
1371 try {
1372 osw = new BufferedWriter(new OutputStreamWriter(os, "UTF-8"));
1373 //System.out.println("@@@ SENDING LINE: " + inputstr);
1374 osw.write(inputstr, 0, inputstr.length());
1375 osw.newLine();//osw.write("\n");
1376 osw.flush();
1377
1378 // Don't explicitly send EOF when using StreamGobblers as below,
1379 // as the EOF char is echoed to output.
1380 // Flushing the write handle and/or closing the resource seems
1381 // to already send EOF silently.
1382
1383 /*if(Misc.isWindows()) {
1384 osw.write("\032"); // octal for Ctrl-Z, EOF on Windows
1385 } else { // EOF on Linux/Mac is Ctrl-D
1386 osw.write("\004"); // octal for Ctrl-D, see http://www.unix-manuals.com/refs/misc/ascii-table.html
1387 }
1388 osw.flush();
1389 */
1390 } catch (IOException ioe) {
1391 log("Exception writing to SafeProcess' inputstream: ", ioe);
1392 } finally {
1393 SafeProcess.closeResource(osw);
1394 }
1395 }
1396
1397 // call the user's custom handler for the run() method
1398 public void runCustom() {
1399 this.customHandler.run(os);
1400 }
1401
1402 public void run()
1403 {
1404 if(this.customHandler == null) {
1405 runDefault();
1406 } else {
1407 runCustom();
1408 }
1409 }
1410} // end static inner class OutputStreamGobbler
1411
1412//**************** Static methods **************//
1413
1414
1415 // logger and DebugStream print commands are synchronized, therefore thread safe.
1416 public static void log(String msg) {
1417 if(DEBUG == 0) return;
1418 logger.info(msg);
1419
1420 //System.err.println(msg);
1421
1422 //DebugStream.println(msg);
1423 }
1424
1425 public static void log(String msg, Exception e) { // Print stack trace on the exception
1426 logger.error(msg, e);
1427
1428 //System.err.println(msg);
1429 //e.printStackTrace();
1430
1431 //DebugStream.println(msg);
1432 //DebugStream.printStackTrace(e);
1433 }
1434
1435 public static void log(Exception e) {
1436 logger.error(e);
1437
1438 //e.printStackTrace();
1439
1440 //DebugStream.printStackTrace(e);
1441 }
1442
1443 public static void log(String msg, Exception e, boolean printStackTrace) {
1444 if(printStackTrace) {
1445 log(msg, e);
1446 } else {
1447 log(msg);
1448 }
1449 }
1450
1451 public static String streamToString(int src) {
1452 String stream;
1453 switch(src) {
1454 case STDERR:
1455 stream = "stderr";
1456 break;
1457 case STDOUT:
1458 stream = "stdout";
1459 break;
1460 default:
1461 stream = "stdin";
1462 }
1463 return stream;
1464 }
1465
1466//**************** Useful static methods. Copied from GLI's Utility.java ******************
1467 // For safely closing streams/handles/resources.
1468 // For examples of use look in the Input- and OutputStreamGobbler classes.
1469 // http://docs.oracle.com/javase/tutorial/essential/exceptions/finally.html
1470 // http://stackoverflow.com/questions/481446/throws-exception-in-finally-blocks
1471 public static boolean closeResource(Closeable resourceHandle) {
1472 boolean success = false;
1473 try {
1474 if(resourceHandle != null) {
1475 resourceHandle.close();
1476 resourceHandle = null;
1477 success = true;
1478 }
1479 } catch(Exception e) {
1480 log("Exception closing resource: " + e.getMessage(), e);
1481 resourceHandle = null;
1482 success = false;
1483 } finally {
1484 return success;
1485 }
1486 }
1487
1488 // in Java 6, Sockets don't yet implement Closeable
1489 public static boolean closeSocket(Socket resourceHandle) {
1490 boolean success = false;
1491 try {
1492 if(resourceHandle != null) {
1493 resourceHandle.close();
1494 resourceHandle = null;
1495 success = true;
1496 }
1497 } catch(Exception e) {
1498 log("Exception closing resource: " + e.getMessage(), e);
1499 resourceHandle = null;
1500 success = false;
1501 } finally {
1502 return success;
1503 }
1504 }
1505
1506 public static boolean closeProcess(Process prcs) {
1507 boolean success = true;
1508 if( prcs != null ) {
1509 success = success && closeResource(prcs.getErrorStream());
1510 success = success && closeResource(prcs.getOutputStream());
1511 success = success && closeResource(prcs.getInputStream());
1512 prcs.destroy();
1513 }
1514 return success;
1515 }
1516
1517// Moved from GShell.java
1518 /** Determine if the given process is still executing. It does this by attempting to throw an exception - not the most efficient way, but the only one as far as I know
1519 * @param process the Process to test
1520 * @return true if it is still executing, false otherwise
1521 */
1522 static public boolean processRunning(Process process) {
1523 boolean process_running = false;
1524
1525 try {
1526 process.exitValue(); // This will throw an exception if the process hasn't ended yet.
1527 }
1528 catch(IllegalThreadStateException itse) {
1529 process_running = true;
1530 }
1531 catch(Exception exception) {
1532 log(exception); // DebugStream.printStackTrace(exception);
1533 }
1534 return process_running;
1535 }
1536
1537} // end class SafeProcess
Note: See TracBrowser for help on using the repository browser.