CRITICAL: LinuxProcessManager kills ALL processes

[GoogleCodeExporter]

If the office process couldn't be started, OfficeProcess.pid stays at value 
PID_UNKNOWN. As no check is performed, this id is used to stop the process (due 
to ManagedOfficeProcess.stopAndWait or restartAndWait for instance). 

As PID_UNKNOWN = -1, it ends with a kill -KILL -1 and according to man kill:

kill -9 -1
              Kill all processes you can kill.

Original issue reported on code.google.com by mguille...@yahoo.fr on 7 Dec 2011 at 10:16

Attachments:

• LinuxProcessManagerKill-1.patch

[GoogleCodeExporter]

What? kill -1 kills all processes? Damn, this is probably the most embarassing 
bug I've ever written. :-/

Patch accepted as defensive, but we still need to 1. understand why the pid 
could not be found (never seen this on Linux); and 2. ideally fail fast rather 
than deferring the error until the first restart.

Original comment by mirko.na...@gmail.com on 7 Dec 2011 at 8:28

• Changed state: Started
• Added labels: OpSys-Linux, Priority-Critical, Target-3.0-beta-5, Type-Defect, Version-3.0-beta-4

[GoogleCodeExporter]

Issue 95 has been merged into this issue.

Original comment by mirko.na...@gmail.com on 7 Dec 2011 at 8:32

[GoogleCodeExporter]

I was bluffed reading the effect of kill -9 -1 too!

The patch is not ideal, I agree. The reason why the PID couldn't be determined 
is that startup failed because an older office process was still here.

Original comment by mguille...@yahoo.fr on 8 Dec 2011 at 8:07

[GoogleCodeExporter]

I still can't reproduce the issue. If an older process is still running then 
starting a new one should fail with something like

IllegalStateException: a process with acceptString 
'socket,host=127.0.0.1,port=2002' is already running; pid 7843

There must be some situation in which LinuxProcessManager.findPid() fails to 
detect an existing process, but I'm not sure exactly how.

Original comment by mirko.na...@gmail.com on 1 Jan 2012 at 4:19

[GoogleCodeExporter]

Change in r220 to fail fast if the pid cannot be found.

Original comment by mirko.na...@gmail.com on 1 Jan 2012 at 4:56

• Changed state: Fixed

[GoogleCodeExporter]

Issue 104 has been merged into this issue.

Original comment by mirko.na...@gmail.com on 19 Feb 2012 at 9:56

[GoogleCodeExporter]

The scenario is the folloning:
We are using a single X-Server and work with a few Clients on it.
We have the jodconverter within a jboss, meaning we start the manager together 
with the jboss. If 2 people start their jboss, only the first one will succeed 
in starting it fully, the second one will receive a message like:
IllegalStateException: a process with acceptString 
'socket,host=127.0.0.1,port=2002' is already running; pid 7843
This doesnt stop the jboss with the not correctly started jodconverter from 
calling the shutdown-methodes of jodconverter when it is asked to shutdown, 
resulting in the user getting logged out from x completely.

Original comment by cola_co...@ki.tng.de on 19 Feb 2012 at 1:32