While activating a number of the Jini services, activation hangs at
   the call to UNIXProcess.forkAndExec. This hang has been observed on
   jdk1.3 for linux. Below, an excerpt of a thread dump is included showing
   UNIXProcess.forkAndExec not returning.
                               .
                               .
                               .
"RMI TCP Connection(2908)-129.148.70.134" daemon prio=1 tid=0x48812398
                                  nid=0x5dc runnable [0xb95fe000..0xb95ffac4]
   at java.lang.UNIXProcess.forkAndExec(Native Method)
   at java.lang.UNIXProcess.<init>(UNIXProcess.java:137)
   at java.lang.Runtime.execInternal(Native Method)
   at java.lang.Runtime.exec(Runtime.java:551)
   at java.lang.Runtime.exec(Runtime.java:477)
   at java.lang.Runtime.exec(Runtime.java:443)
   at sun.rmi.server.Activation$GroupEntry.getInstantiator(Activation.java:1181)
   at sun.rmi.server.Activation$GroupEntry.activate(Activation.java:1088)
   at sun.rmi.server.Activation$ActivatorImpl.activate(Activation.java:260)
   at java.lang.reflect.Method.invoke(Native Method)
   at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
   at sun.rmi.transport.Transport$1.run(Transport.java:142)
   at java.security.AccessController.doPrivileged(Native Method)
   at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
   at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)
   at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run
                                                       (TCPTransport.java:643)
   at java.lang.Thread.run(Thread.java:484)
                               .
                               .
                               .
   We believe this bug also occurs on jdk1.2.2 for linux, but bug 4353439
   prevents us from verifying this.

   The full thread dump is attached separately.