Re: Thread and Garbage collection

Thanks very much! What's your mean: "which BTW sets  *INTERRUPTED* flag in the Thread object, The use of the an instance variable is redundant since the thread already has a flag designed for that perpose." I also think this is a feasible way. Because I think the root for garbage collection are i

Re: 2 JNI questions

> Vasile GABURICI writes: Vasile> Dear Blackdown developers, Vasile> I know that your time is precious, so I have only two Vasile> questions regarding the interaction between a C Vasile> application using Linux kernel threads and your JDK Vasile> 1.2.2-RC4: Vasile> 1

Re: Thread hangs, signals and JNI

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

Re: Thread hangs, signals and JNI

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

Re: Thread and Garbage collection

In a previous post I made an error in the code example it should look like the following. Allowing for the thread acsessing the hashtable extracting the referenenced Thread object and calling Thread.interupt() , which BTW sets  *INTERRUPTED* flag in the Thread object, The use of the an

Re: Thread hangs, signals and JNI

>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

Re: Thread hangs, signals and JNI

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.

2 JNI questions

Dear Blackdown developers, I know that your time is precious, so I have only two questions regarding the interaction between a C application using Linux kernel threads and your JDK 1.2.2-RC4: 1) What *exactly* is permitted and what is not with respect to threads and sign

Re: using jdb within Emacs/JDE

Questions on JDE are more properly directed at the JDE mailing list: [EMAIL PROTECTED] There is a helpful archive of this list at http://www.mail-archive.com/jde@sunsite.auc.dk/maillist.html. Your problem stems from the fact that the jdb that is shipped with the latest 1.2 JDKs on linux is of a

Re: Thread and Garbage collection

I am assuming you are using jdk1.2 and in that case the stop method has been depricated. You should use use Thread interrupt to stop the thread. When you remove the Thread object from the hashtable issue a Thread.interrup() call so the thread object unwinds correctly and exits the run method then

Re: Thread hangs, signals and JNI

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

Thread hangs, signals and JNI

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