JWeb and System.exit()

I hope someone can help with this question:

I'm running OAS 4.0.7 Enterprise using the Jweb cartridge to instantiate a large Object, then pass it serialized across the HTTP connection to the applet that's making the connection using an ObjectOutputStream.

My question is this, the Object includes references to AWT components which are set to null, but it seems to start the AWT event and GUI threads anyway. When I run the JWeb class as a standalone (since JWeb uses the public static main (String[] args) signature the same as a standalone) the process does not exit when it gets to the end of main() because of the AWT threads (my guess). Usually in a standalone with AWT components, you would call System.exit(0) to exit the program when they close the window, etc., but I'm wondering what I should do with the JWeb cartridge, though... If I call System.exit(0), will it kill the JVM in the Application Server? The closest thing to a discussion I can find in the Jweb docs is it saying not to close() streams based on System.out or System.err, but no mention of System.exit().

I don't want my JWeb cartridge requests to hang, like the command line invocation of the class, but I don't want to bring the server down, either... any ideas?

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Tue Aug 17 1999 - 14:03:52 CDT