Re: [Smartfrog-support] Termination due to slow start-up.
Ismael Juma <[email protected]> Fri, 15 Feb 2008 15:16:51 +0000
| Newsgroups | gmane.comp.java.smartfrog.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Fri, 2008-02-15 at 15:15 +0000, Steve Loughran wrote: > What is interesting is that even in that interval, say 1000mS, if the > child goes live, this fact is remembered -and from then on, failing a > ping is a cause for concern. Unlike the Delay component, which doesnt > start its child for a given period, SlowStart starts it, but doesnt > expect it to go live. Interesting. As I outlined in my original message, this is the behaviour I was expecting, probably due to my web container bias. > Given that this slow starting is possibly a common behaviour of all web > applications, I'm thinking of patching it in to all of them, rather than > requiring all deployments to be wrapped in SlowStart declarations. I'd > have a base delay for the application server, a value which could be > overridden by an explicit delay for the webapp/ear or anything else that > you deploy. +1 from me. Thanks, Ismael ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/