I ran into a rather annoying problem with this library. Perhaps someone else
could confirm the same problem. I wrote a rather large distributed threaded
network management system. When the system was started up lots of log messages
were sent via tcp to a logging server, and the rest of the system was
functioning fine. After I added the very simple code to catch SIGTERM and
SIGINT, the system logged only a few messages and proceeded to hang. After
removing the code to initialize the signalListener the system once again worked
as designed.
I played a bit with the jni library, but ended up not using it do to the
problem above. I thought that the jvm was using signals in some way to handle
something, but I did not look into it any more.
If anyone has any ideas on why this may be occurring or if the jvm indeed does
use signals in some odd way please let me know.
--jason
On 28-Sep-98 John Baker wrote:
> On Mon, Sep 28, 1998 at 10:00:45AM -0400, Nelson Minar wrote:
>> >What I would like is just a very simple SignalCatcher for SIGTERM,
>> >SIGQUIT, SIGHUP and SIGINT: just four signals. I want to catach them
>> >in Java, and write the capture to a systems log. So that at least
>> >overnight personnel would know how my java batcher died .
>>
>> Someone wrote just that for Linux recently, it was posted to this
>> list. I don't know what, though. Hopefully the list is archived somewhere?
>
> http://interstice.com/~kevinh/projects/javasignals/
>
>
>
> -John
>
> --
> John Baker, Software Engineer, Java coder, Salad sarnie lover.
> Work: (01203) 562000 ext 4153
> Home: (01203) 601890
