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>
Won't work.
I removed the parameters from the kerneel and put them into merlin.properties (and yes - I know - I still havn't updated the docs). Just set the following parameter to modify the default timeout duration:
merlin.deployment.timeout
CHeers, Steve.
See http://avalon.apache.org/merlin/meta/kernel/parameters/index.html
--------------------------------------------------------------------- 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]
