Native routines/SIGALRM on Sun

Posted on 1997-04-14
Last Modified: 2013-11-21
I have an old legacy database interface system that uses message queues to communicate.  We have a Java application that we are trying to write to retrieve information from this database using this legacy system.  The native calls to this system were crashing, and I finally found out why.  The call to the system call msgrcv() was being interrupted by a signal - SIGALRM (14) to be exact.  I theorized that this had something to do with the mouse movements/event-type structure of Java and I think I'm right.

O/S is Sun, Solaris 2.3.  We're using JDK1.1.1

To prevent the problem, I tried to ignore the signal (or trap it) just before the msgrcv() call and restore it after the call.  Every time I do this, the msgrcv() calls works fine, but the Java VM crashes giving me the single message: "Alarm Clock" on stdout.  I have written a very small Java application and native routine (which does nothing but trap and restore this signal when it gets called) and each time the VM crashes with this error.  So far, the work-around has been to simply retry the system call for some MAX times until it either works or fails MAX times.  While this works so far, I don't know what other system calls may fail.  And this seems to be a silly work around.

The question then is, how do I make a native call from Java while ignoring any signals so that the VM doesn't crash?
Question by:dennist041497
  • 2
  • 2

Expert Comment

ID: 1219555
I think you're wrong about the source of the alarm signal.  Are you reverse-engineering the C-interface to the database?  Does the database have a name?

It's common to set an alarm to interupt a call to msgrcv, since UNIX provides no other mechanism to block the request for a duration between instantaneous and infinite (excusive).  I can't say that the Solaris JVM is NOT setting an alarm, but it seems like a less likely scenario, given the symptoms you present.

Author Comment

ID: 1219556
I'm right about the source of the signal.  I can get the signal to happen only if I move the mouse after pressing the button on the Java app that calls the native routine.  If the mouse is still, no alarm happens (or happens *very* seldom).  Besides, I have a very small C routine (no database calls, just signal handling), that traps the SIGALRM signal and that signal fires when I move the mouse around (only that signal, by the way).

The database is Informix, but that's irrelevant.  Many years ago, our company wrote a database interface, in C, so that many processes could concurrently use the database (Ingres at the time) without bringing down the system.  The interface was built to be database independent so that if we did change databases (and we did), the applications would not have to change.  The msgrcv() call never is interrupted with our C programs that send messages to this interface, presumably because we never generate such a signal.  But now, Java is also in the picture.  And, with the evidence of the mouse moves... I'd say that's fairly conclusive.  

I did get a note from a newsgroup that says I should probably use the jacket routines provided in the green threads package to do system calls.  I'll have to research this.

Thanks for responding.  Hope this helps clarify my situation.

Accepted Solution

JWBito earned 200 total points
ID: 1219557
I suppose that it would be a good idea to use the Solaris JVM from SunSoft rather than JavaSoft's.  I imagine that the newer, optimized JVM from SunSoft wouldn't need to resort to SIGALRM to handle timing of mouse-events...

I believe that most threading packages can be made to limp along if you block the signals that they use during system calls.

I suggest
sigset_t set;
sigaddset(set, SIGALRM);
sigprocmask(SIG_BLOCK, set, NULL);
sigprocmask(SIG_UNBLOCK, set, NULL);

I hope this helps!

Author Comment

ID: 1219558
The answer seemed to work, although the code needs to be modified as stated in the answer.  All the calls need a pointer to the set, rather than the set itself.  Other than that, I believe this work around may help.

The Solaris version of the JVM is only compatible with 1.0.2 of the JDK and won't meet our needs (as we need RMI).

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How to parse custom JSON to POJO java 4 52
topping2 challenge 13 80
Ways to assess https/ssl websites 3 83
eclipse formatting 6 70
Article by: kevp75
Hey folks, 'bout time for me to come around with a little tip. Thanks to IIS 7.5 Extensions and Microsoft (well... really Windows 8, and IIS 8 I guess...), we can now prime our Application Pools, when IIS starts. Now, though it would be nice t…
Java functions are among the best things for programmers to work with as Java sites can be very easy to read and prepare. Java especially simplifies many processes in the coding industry as it helps integrate many forms of technology and different d…
Viewers will learn about the different types of variables in Java and how to declare them. Decide the type of variable desired: Put the keyword corresponding to the type of variable in front of the variable name: Use the equal sign to assign a v…
Viewers will learn one way to get user input in Java. Introduce the Scanner object: Declare the variable that stores the user input: An example prompting the user for input: Methods you need to invoke in order to properly get  user input:

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now