Hi, just a question - is this the same parameter that you can set by adding "merlin.deployment.timeout = 1000000" to your merlin.properties?
Is there a possibility to set the deployment timeout per component instead of the container? Thanks /peter > -----Ursprungligt meddelande----- > Fr�n: Timothy Bennett [mailto:[EMAIL PROTECTED] > Skickat: den 11 februari 2004 23:03 > Till: [EMAIL PROTECTED] > �mne: Re: Deployment timeouts > > > De Lima, Claude wrote: > > I'm trying to run a server we've developed under the latest > bleeding-edge > > checkout of Merlin > > from CVS and am getting the following timeouts. This server ran > > successfully under merlin 3.0. > > Do we need to set deployment timeouts on a component basis? > If so, how is > > this done? > > > > Try adding the following to your kernel.xml file: > > <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> > > See http://avalon.apache.org/merlin/meta/kernel/parameters/index.html > > > --------------------------------------------------------------------- > 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]
