This week's book giveaway is in the Testing forum. We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line! See this thread for details.
When you kill it, you kill it. Nothing will be done after that point.
It sounds like your program reaches deadlock. I'm guessing this is because you're making changes to your GUI from another thread than the Event Dispatch Thread (EDT).
Put a few println statements in your program to identify where it hangs, and then post that part, and we can have a look at it.
Yes. Be careful though that you kill the right java process. If you have multiple JVMs active they will all show up as "java" in the Windows task manager.
Running from the command line as I suggested earlier can give you a workaround. As long as the JVM is running the java command does not end. If you press CTRL+C in that command prompt window it will also terminate your application.
Well, Ramesh, then you'll have to settle with advice.
It sounds like a deadlock. See what threads you are using, and where in your code they interact. By interact I mean, where do they work on the same objects?
I have a feeling you are making updates to the GUI in a thread other than the EDT. Are there any Swing component methods you are calling from a thread other than the EDT?
Here's a mistake I would often make: Some event happens in your GUI, and you create a new thread in the listener to handle it, so the EDT can continue and your GUI will remain responsive. Your new thread will work on some data, which is fine, but then you add new items to a JComboBox or something like that, from the same thread.