Ensure OOo process is always terminated on *nix systems

bparreira17 / jodconverter

Automatically exported from code.google.com/p/jodconverter

0 stars 0 forks source link

Ensure OOo process is always terminated on *nix systems #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Using Process.destroy() to terminate the OOo process doesn't guarantee that
the process is always terminated.

Process.destroy() sends a normal SIGTERM, but in some (infrequent but
possible) cases OOo may not respond and require a SIGKILL.

It's possible to kill a process from Java using introspection to get the
pid from java.lang.UNIXProcess and then invoking the external kill command.
 Ugly, but should work.

Original issue reported on code.google.com by mirko.na...@gmail.com on 1 Jun 2008 at 6:46

GoogleCodeExporter commented 8 years ago

Original comment by mirko.na...@gmail.com on 1 Jun 2008 at 7:02

Added labels: Priority-Critical
Removed labels: Priority-High

GoogleCodeExporter commented 8 years ago

Thanks, that will be really helpfull.

Original comment by Gount...@gmail.com on 2 Jun 2008 at 10:24

GoogleCodeExporter commented 8 years ago

Original comment by mirko.na...@gmail.com on 20 Jul 2008 at 1:13

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Great, thanks.

Original comment by Gount...@gmail.com on 21 Jul 2008 at 10:20

GoogleCodeExporter commented 8 years ago

Original comment by mirko.na...@gmail.com on 27 Mar 2011 at 1:21

Changed state: Released