that the Java level signal API
> is private interface. Its sole purpose is to implement the shutdown
> mechanism (see Runtime.addShutdownHook). The interface may change
> or get dropped completely without notice in future JDK. So use at
> your own risk. (If you really want to catch si
rpose is to implement the shutdown
mechanism (see Runtime.addShutdownHook). The interface may change
or get dropped completely without notice in future JDK. So use at
your own risk. (If you really want to catch signals, it's better
to write JNI code; signals have well-defined behavior at C leve
Ah, the IBM JDK was holding the signals for the JVM, that explains why
that didn't work (had to use -Xrs).
Works with 2.6:
IBM 1.3.1-6 (with -Xrs)
Sun 1.4.2_03 (no -Xrs)
Does Not Work with 2.6:
Blackdown 1.3.1
Sun 1.3.1_10
Sun 1.3.1_11
Untested:
Blackdown 1.4.x
IBM 1.4.x
Everything t
The IBM JRE did not appear to catch the signals at all, they get passed
right through and kill the application.
Once I have something that tests the signals exclusively, hopefully I can
test all three of the JVMs and see what happens.
At 12:13 on Mar 16, Tony Reix shook the earth with:
>
No, I haven't tried the IBM JVM. That's a good idea.
At 12:13 on Mar 16, Tony Reix shook the earth with:
> Hi Nicole,
>
> { ...
> { I will be constructing a basic application that just does the signal
> { handling similar to my application so I can use it to test.
>
> Seems your problem is not e
Hi Nicole,
{ ...
{ I will be constructing a basic application that just does the signal
{ handling similar to my application so I can use it to test.
Seems your problem is not easy to understand ...
Let us know when you have built such a basic application. At that
time we'll try to reproduce it
Assume 100.
Which I noted on google groups could be caused by SMP, so I tried a
non-SMP kernel, to no avail. Then, I dug deeper, upgraded my version of
"procps" to a later version, and tried again. No luck with the signals,
but the "Unknown HZ" message went away. I'm reall
Tony, Sebastien, List,
At 09:10 on Mar 11, Tony Reix shook the earth with:
> Hi Nicole,
>
> Would it be possible for you to extract the code that produces the
> problem and provide a very small program we could use in our labs
> in order to reproduce the problem with our environment (RedHat 9,
>
Hi Nicole,
{ ...
{ I upgraded my kernel to version 2.6, and now it looks like these signals
{ aren't being caught anymore -- sort of.
{ ...
{ I've been using blackdown 1.3.1, but as a test I switched to Sun's
{ 1.3.1_10 and am still having the same problem.
{ ...
{ I assumed
I have an application that has signal handlers registered for signals 11,
15, and 2. When these signals are received, I print out that I caught the
signal, call some "dump to disk" functions for what's in memory, then I
System.exit().
I upgraded my kernel to version 2.6, and no
PROTECTED]> on 29/05/2001 13:59 MST
To: [EMAIL PROTECTED]
cc:
Subject: Signals, JNI and sigtimedwait()...
Okay, I'm writing some JNI code for some stuff using RT signals. I need to
do some sigtimedwaits, which then post as IO events to the JVM. My original
design was to have J
Okay, I'm writing some JNI code for some stuff using RT signals. I need to
do some sigtimedwaits, which then post as IO events to the JVM. My original
design was to have Java threads invoke something like waitForIO(), which
was a native method which did the sigtimedwait(). Unfortunately,
Hi,
I want to know more about the signals and the doccumentation in Linux, where
can I get it???
I looked at the signal.h in the /usr/include directory does not have all
the info.
I get signals 32 and 38, while running my applications.
let me know if any one has some info for me.
regards
> Vasile GABURICI writes:
Vasile> I am not questioning your knowledge on the SIGUSR2 issue,
Vasile> but note that other JVMs do not seem to use it. For
Vasile> instance Sun's JDK 1.2.2 for Linux does NOT use SIGUSR2. I
Vasile> have checked the source. Unfortunately their
V
use
I've missed the introduction of real time signals in glibc 2.1 ;-( Too bad
that the only notice went into the NEWS file. No documentation so far...
When I was strace-ing the JDK, it seemed strange to me that I was getting
all the SIG_RTx stuff...
Unfortunately, my work is now comple
Vasile> by launching new connection threads. After that, main()
Vasile> calls NsHandleSignals where it stays until the server is
Vasile> shut down. Therefore, all threads that will call the JVM
Vasile> will have the SIGHUP, SIGPIPE, SIGTERM, SIGINT and SIGUSR2
Vasile>
will have the SIGHUP, SIGPIPE, SIGTERM, SIGINT and SIGUSR2 signals
masked.
One cannot expect a web server not to handle signals like SIGHUP
or TERM, so I don't see why this is "bad, bad, bad" in principle. The fact
that the JVM expects to run alone and handle all signals
natives.
Actually, I believe the Linux thread support in glibc no longer uses SIGUSR1
& 2.
It's more likely his problem is coming from masking all those signals (bad,
bad, bad) which the JVM needs to have available to it.
The AOLServer's sigwait() is essentially the source of your
T code, it would make the AOLServer not usable as a daemon.
TIA,
Vasile
On Wed, 17 May 2000, Ramesh Thummala wrote:
> Vasile,
> I had some painful experiences with the Blackdown JDK 1.2.2-RC4 with respect to
>signals. It looks like Blackdown JVM is using SIGUSR1 and
Vasile,
I had some painful experiences with the Blackdown JDK 1.2.2-RC4 with respect to
signals. It looks like Blackdown JVM is using SIGUSR1 and SIGUSR2 to suspend the JVM
threads while garbage collector starts collecting garbase. During this process, rest
of the JVM threads(exceopt
Hello Blackdown developers,
Abstract of this rather long message:
What exactly is allowed and what is not with respect to signals in
a multithreaded application that uses the Blackdown 1.2.2-RC4 JDK on
Linux? I am experiencing random thread hangs inside the JVM. When
want server.shutdown(); // and exit cleanly System.exit(0); } } }
==excerpt ends here==
- Original Message -
From: "Chris Kelly" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, March 30, 200
o any one of the other
> unix-signals?
>
> I would like to be able to interrupt a server through kill signals, but would
> like that it makes some salvages before going down
>
>
--
To UNSUBSCRIBE, emai
one of the other
>unix-signals?
oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo0oo
Send Sun a Message!
Vote for JConfig in the JDJ Readers' Choice Awards.
http://www.sys-con.com/java/readerschoice2000/
> How can I make a method being called before the jvm exits when killing
> the jvm (or pressing Ctrl-C if its in the foreground)?
I believe you need to handle it using JNI and calling C code (not very
portable)
The following software does this for you:
http://interstice.com/~kevinh/project
nals available on the blackdown site at
http://www.blackdown.org/java-linux/otherproducts.html
that is poiting to the site:
http://interstice.com/~kevinh/projects/javasignals/
it is working fine with me, but i'm afraid it is platform dependant as i
don't have a clue wether other OS that a
There is a method in System called runFinalizersOnExit(boolean) that
supposedly will let you tell the jvm to run all finalizers when the jvm is
shut down. However, I've heard it's not that reliable, and I notice that
it has been deprecated in jdk1.2.
On Tue, 8 Jun 1999, Jonas Holmberg wrote:
How can I make a method being called before the jvm exits when killing
the jvm (or pressing Ctrl-C if its in the foreground)?
I suppose a pure java way is out of the question? What is the least OS
dependant way?
What I want is to do some cleanup before stopping a server written in
java only. And
Peter Kovacs wrote:
>Is there any facility (Java API call) which can be used to catch operating
>system signals sent to the Java Virtual Machine and do whatever deemed
>necessary upon reception of a specific signal?
There isn't anything as standard. Perhaps this will help, th
Is there any facility (Java API call) which can be used to catch operating system
signals sent to the Java Virtual Machine and do
whatever deemed necessary upon reception of a specific signal?
Any help appreciated.
Peter
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
Last week Trent Jarvi wrote:
> http://www.interstice.com/~kevinh/projects/javasignals/index.html
Hi Kevin
I will let you know if I get this working with Solaris,
but it is low priority at the mo ...
Cheers
Peter
--
import java.std.disclaimer.*; // "Dontcha just love the API, baby
Hi all gurus!
> [EMAIL PROTECTED] wrote:
>
> > Can Java catch signals ?
> >
> > Could the Java Native Interface be used to help Java catch signals ?
> >
> > * prelim design in my head *
> > I have a huge script that run configurable batch jobs sequentl
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
>
>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 j
[EMAIL PROTECTED] wrote:
> yes, u can do that, but the underlying native I/O already uses SIGNALS to catch
>SIGIO,
> SIGALRM which is used to impliment the green_threads/context switching of java (fake)
> threads. So be carefull what sigs u catch, or turn off.
>
>
How woul
http://www.interstice.com/~kevinh/projects/javasignals/index.html
Trent Jarvi
[EMAIL PROTECTED]
Can Java catch signals ?
Could the Java Native Interface be used to help Java catch signals ?
* prelim design in my head *
I have a huge script that run configurable batch jobs sequently over several hours.
I would like to rewrite the damn thing in Java, so that I could write module
to display
38 matches
Mail list logo
