The JVM will also die if it crashes. E.g. you might have a JNI library you are using and it has a bug in its shutdown/unload. Have a look for a hs_err_pid*.log file in the working directory of your instance.
Otherwise, you really are calling System.exit() if not directly. In which case you should be able to debug your instance and breakpoint this call to see if it being called. AFAIK, Even if all your thread are daemons, felix has threads which are not so this is unlikely to be the cause of your problem. -----Original Message----- From: Felix Meschberger [mailto:[email protected]] Sent: 16 September 2010 12:40 To: [email protected] Subject: Re: Stopping and non daemon threads Hi, Well, the JVM can of course only exit after all non-daemon threads have been stopped or after a call to System.exit(int). Now, if you have a bundle which starts a thread, you must make sure to stop that thread when the bundle stopped. Otherwise you create a memory and performance leak if the bundle is repeatedly started, stopped, updated etc. Regards Felix Am 16.09.2010 13:01, schrieb Damian Minkov: > Hi, > > I'm currently looking at a problem in sip-communicator on shutting > down. To shut down we stop bundle with id 0. But in some of our > bundles we need to do some stuff which involves network operations, > and so we create a non daemon Thread in order to do it. But just a > little after the Thread is created and started the application exits > and don't finish all the operations. > Any ideas why this happen or just am I missing some configuration? > > Thanks > damencho > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
