> 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
Dear Juergen,
Thanks a lot for the 1st class analysis and solution for this
problem. You've made my day :-) I've implemented the fix you proposed, and
all is fine now with Blackdown JDK 1.2.2.
Apparently, I've been living on another planet lately, because
I've missed the
Hi Vasile,
Vasile> The AOLServer code for signal handling is very simple. The
Vasile> functions NsBlockSignals and NsHandleSignals are included
Vasile> bellow. These functions contain all the signal handling
Vasile> that is relevant to this issue. AOLServer does more funny
V
The AOLServer code for signal handling is very simple. The
functions NsBlockSignals and NsHandleSignals are included bellow. These
functions contain all the signal handling that is relevant to this issue.
AOLServer does more funny things when it exec()s an external program, but
I am not e
>If you make sure, you do not mask your SIGUSR1 and SIGUSR2,
>you should be able to run fine. However, there is one caveat. Linux
>threads use SIGUSR1 and SIGUSR2 for their internal
>communication in some products. If your >product also uses them,
>you should see for alternatives.
Actually, I
Dear Ramesh,
Thanks for the tips. I did make some progress, but did not solve
the problem.
Abstract:
Sending *any* signal that is blocked by the connection threads
(the only ones that attach to the JVM), but that is handled by the main
thread, unblocks the JVM.
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 garbag
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 that
