Description:
Symptoms
========
If a Java application launches a rvd on UnixWare 7.1.3 and then for some reason the application is killed, rvd should die automatically after &gt2 minutes.  However, this does not happen - the process still exists but appears to be unresponsive.  If you restart the application, which will attempt to connect to the daemon, the API reports "java.lang.OutOfMemoryError: Out of memory".

Impact
======
Loss of Functionality

Workaround
==========
It is possible to work around this defect by simply starting the daemon itself i.e. do not have the application launch the daemon.

Cause
=====
The specific version of Java, 1.3.1, for UnixWare utilizes SIGUSR1 signal for its operation. Java blocks SIGUSR1 before auto-spawning rvd.  rvd inherits the signal mask from its parent process, so rvd still has its SIGUSR1 blocked. rvd requires properly operating SIGUSR1 to correctly shut down service once the last client disconnects.

Resolution
==========
This is expected to be fixed in an upcoming patch for TIBCO Rendezvous 7.2 - called Patch 7.2.2.


Symptoms:

Cause:

rvd 7.2 becomes unresponsive on UnixWare 7.1.3 with Java 1.3.1.