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]
