#41 jMax behaves badly if server not present

[Carl Seleborg]

This bug arises when jMax is launched with the
-jmaxServerName option indicating a non-existent
program (like this :

jmax -jmaxServerName "echo"

This will try to start the program echo in FTS'
directory, which will fail).

Once the interface has reported the exception, which
looks like this (stack trace left aside) :

java.io.IOException: java.io.IOException:
/path_to_fts/echo: not found

it sits around waiting for user input and tries to act
like the FTS server was there, which results in
exceptions beeing thrown, even when trying to quit the
application. Thus, the user is "stuck" and has to
"killall java" under linux to get out of it.

[Carl Seleborg]

Logged In: YES
user_id=783606

A similar problem occurs when using a socket to connect the
client to FTS.

1. Launch fts from the command-line (no args)
2. Launch jmax with following command-line :
jmax -jmaxConnection socket -attach true

This will attach the GUI to the running FTS server. But if
the server dies, the GUI does not detect it, and exceptions
start pooring when trying to do something.