-----Original Message----- From: [EMAIL PROTECTED] on behalf of Nico Klasens Sent: Fri 1/9/2004 11:16 AM To: [EMAIL PROTECTED] Cc: Subject: RE: email application does not start threads as daemon > Kees Jongenburger <[EMAIL PROTECTED]> wrote: > > Code in the email application does not start threads a daemon , this > prevents mmbase from restarting correctely after a "touch web.xml" > > I was wondering if this rule is not a bit the absolute. I think that > threads > which are garanteed to stop in a a relativily short time by them self > could > logically just as well not be a daemon, and can simply finish their job > first if someone touches web.xml. that's exactely the probem while one thread stops mmbase creates a new "ModuleProbe" thread and it looks like you have to way untill all threads stop at te same time (I'm not shure) moost mmbase of the mmbase threads (all the callback) typicaly wait for a few minutes
Threads in mmbase are never stopped. and the whole appserver is a daemon > > Is there any other difference between daemon and non-daemon threads > besides > this specific property of them (perhaps in terms of efficiency)?
<<winmail.dat>>
