Thanks, setting the merlin property seems to work just fine! One other thing: Niclas mentioned something about setting timeout per component (see below). We have a situation where one life cycle stage can take different amount of time, since the stage is waiting for a hardware device (where the hardware is specified during configuration stage of the component). It would be great if the timeout could be specified per component basis.
Regards, Tobias > -----Ursprungligt meddelande----- > Från: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Skickat: den 14 januari 2004 03:22 > Till: Avalon framework users > Ämne: Re: merlin doesn't stop even after Ctlr-C - FIGURED IT OUT > > > On Tuesday 13 January 2004 16:22, korosh afshar wrote: > > I hit the Kernel documentation on merlin and found this node: > > > > > > <kernel> > > <parameters> > > <!-- Declaration that deployment should allow for 2500ms for > > any component or container to start-up, before > interrupting > > or failing. --> > > <parameter name="deployment-timeout" value="500" /> > > </parameters> > > </kernel> > > > > > > which will allow me to set that. > > Yes, but I know that Stephen (main guru) is modifying this > since we need to > aggregate the times from many slow starting components, so it will be > possible to define the max start-time for each component, > which will be > properly aggregated for each container. > I don't know the details of this right now. > > > I still need to figure out why maven-merlin plugin doesn't > respond to > > Ctl-C > > "maven-merlin plugin" ??? What are we talking about suddenly? > I must have missed some details. > I thought you said that Merlin couldn't detect Ctrl-C for > your component that > were stuck in initialize().... no? > > > Niclas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -----Ursprungligt meddelande----- Från: Stephen McConnell [mailto:[EMAIL PROTECTED] Skickat: den 3 februari 2004 11:07 Till: Avalon framework users Ämne: Re: Problem with deployment timeout [EMAIL PROTECTED] wrote: > I'm trying to debug an application which is in the process of getting > deployed by merlin, but the deployment timeout is > set to 1000 ms. I tried to change the deployment timeout by adding > > <parameters> > <parameter name="deployment-timeout" > value="100000" /> > </parameters> > > in the kernel.xml file, but merlin does not seem to care. I know that the > kernel.xml > file is processed, because merlin responds to different log settings (debug, > info). My fault! I've moved this to a property in merlin.properties - e.g. merlin.deployment.timeout = 100000 > The merlin version is the almost-latest HEAD from CVS (checked it out > yesterday). > > What more do I have to do to make it work? Just create a merlin.properties file with above property and put the file in either MERLIN_HOME, or ${user.home} or ${merlin.dir}. Steve. > Regards, > Tobias > > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- |------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------| --------------------------------------------------------------------- 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]
