Home/ Questions/Q 56917
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T17:36:35+00:00

Recently I converted a Swing application to Webstart. The process was pretty straightforward, but

  • 0

Recently I converted a Swing application to Webstart. The process was pretty straightforward, but I found that after I close all windows, my application’s JVM did not terminate. The thread dump showed that there are a couple of non-daemon threads, notably Swing’s EDT, AWT and a couple of websart related threads.

The actual strategy used is that each window increments a counter when it is created and decrements one when it is closed. The default close operation is DISPOSE_ON_CLOSE. Wen the counter reaches zero, I stop all threadpools and release all JNI resources.

When I launched the application from a bat file (same JARs), it terminated fine when all windows were closed, so I figured that the problem has something to do with Webstart.

Now the questions:

  1. Can anybody tell me what exactly is happening? Why does Webstart leave zombie JVMs?
  2. Is there a way to release the Webstart resources explicitly without halting the JVM?
  3. I’ve always had the opinion that calling System.exit() encourages the sloppy practice of not releasing your resources and relying on the OS to clean up after you (which can lead to nasty surprises if you reuse the code later)… am I missing something?

See also the followup question for detecting whether the app has been launched by Webstart.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Because of bugs in WebStart, yes. WebStart starts up a ‘secure thread’ for it’s own purposes that interacts with the EDT. This SecureThread prevents the automatic termination of the Java process one would expect when all windows and AWT resources are disposed.

    For more information see http://www.pushing-pixels.org/?p=232

    • 0