forgive me but, I was mistaking maven with merlin.
The below problem occurs when running maven in my impl directory. I tested this with Merlin and it works. Merlin exits with the following message: Exception: org.apache.avalon.activation.appliance.DeploymentException Message: deployment target: [block:/fixgateway] did not respond within the timeout period: [1000] and was successfully interrupted. behaving as you had said. So its while running maven, when this occurs. sorry for the confusion. So my question is: 1 - is it the maven merlin plugin that is outdated that results in this behaviour ? 2 - If my component will take a few seconds to come up due to the fact that it is reliant on other distributed services (messaging service), then how can I prevent merlin from failing the component deployment ? again, sorry for any confusion that might have caused. On Tue, 2004-01-13 at 17:09, Niclas Hedhman wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
