I'm at the end of the rope on this one: I'm developing client JNI interfaces to a RPC server. RPC calls normally have a timer associated on the client side. The timer is defined on the "open client" call. It seems that the RPC library uses alarm() to implement timer management. After invoking the "open client" JNI, the control is released back to Java. Later, when a JNI RPC call is issued, the timer does not work (a RPC call that does not return is not "alarmed"). It seems to me that the Java VM modifies the handling of SIGALRM. Questions: Is this a feature or a bug? I'm using jdk1.1.5v7 on RH 4.2, 2.0.30. If I redefine the behavior of SIGALRM within the JNI will I screw the Java VM? Any info will be greatly appreciated. (My apologies if this is not the proper forum.) -- Diego Pons Pharos Consulting LLC [EMAIL PROTECTED] Los Angeles, CA
