Threads still running after System.exit() call
Hey guys,
I'm kinda stuck in this unusual scenario. The problem is that this only happens inRed Hat 5. There is this application process that I want to kill at the end, so I made thisSystem.exit(). The thing is that this calldoesn't kill all the threads. So, my GUI application gets hung. I can forcefully kill the threads by callingThread.currentTread().stop(), but it's not a pretty and graceful exit. (btw, stop() is deprecated and I'm using 1.5) Any ideas?
Thank you,
-Edwin
[540 byte] By [
Edwin.Ha] at [2007-11-27 6:05:01]
# 2
I know that it does not make sense from your stand point. It also puzzles me, too. The problem is that I'm making that System.exit() call correctly and still experience that. I didn't run into this problem with java 1.4 and 1.6. Also this does not happen in other linux version except Red Hat 5. I know it sounds so unique and weird. I know that there are 4 active threads before I made this call and those 4 threads are not stopped properly. They just hang in there resulting an ugly GUI freeze. And I can only have the count of active threads, not their references. I've tested this with AIX, Suse, Sun OS and windows as well. It works perfectly fine in those enviroments.
