(1.1) Robot tests will not build remotely for JCK: hang on exit from exec'd proc

Robot tests fail JCK batch builds

TEsts which compile and execute without error using JavaTest, will
not batch build. This problem only occurs for tests which run in the
separate process -- or JCK "multiJVM" mode. In building in batch,
display and xhost are correctly set. The tests correctly exec a process,
and actually pass, but they each hang and timeout when they perform a
Status.exit , and report an overall JCK failed status. The overall failure
 reported to the log file is:
 
result: Failed. Program `/re/promoted/jdk/1.3/FCS/L/binary/solaris/
bin/java' interrupted! (timed out?)

The JCK also builds tests in the same JVM space (JCK "singleJVM" mode) and
these tests build without problem. Builds are only done on Solaris.

After the first round of failures, Robot delays were set in the
test and individual tests could be built for the JCK, however,
when run in a small batch of 5, they failed as above. Including
setAutoDelay to the maximum setting as well as setAutoWaitForIDle
did not help. A mix of both auto settings and additional manual
delay produced one success when run in batch but tweaking individual
tests to build is unreliable. Changing the size of the build could introduce
more timing failures if these are timing failures at all.

For individual compiles and executes, these tests do not require any
delays or waits.

It is possible that the autowaits and autodelays do not work for
the remotely exec' process.

It is possibly related to Robot bug 4251318 -- there had been a fix to
allow for remote displays over xconnections.