On Tuesday 13 January 2004 13:45, korosh afshar wrote: > This I figured would result in CLI trappng and starting to go through > shutdown sequence and component decomposition. > > > Without having the above code that was the normal behaviour when I > Ctrl-C'd. > > What I saw, that merlin did not respond to my interrupt command and > continued with the Thread sleep code.
Thanks for the feedback, it is an important case that we must look into. I suspect it is a thread related issue. * Does the code above run in its own thread, i.e. thread is created by the component, or executing this as part of the LifeCycle method calls? * Exactly which version are you using? If it is CVS, then WHEN was it last updated. I believe I can fix this (or might be fixed already) if I get that information. If you could send the whole defunct component, even better... Basically, if it is version earlier than CVS HEAD around 5Jan and it is part of the Life Cycle calls, then the problem should no longer exist. In fact, we have now changed so that Merlin will timeout during the LifeCycle start sequence, if the components takes too long (going to be settable), and aborts by itself. (I will make sure that the shutdown hook is properly interfacing with this new mechanism as well.) Thanks Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
