Re: [Smartfrog-support] Termination due to slow start-up.

[Ismael J. <ml...@ju...>]

Hi Julio,

Thank you for the reply.

On Wed, 2008-02-13 at 10:23 +0000, Guijarro, Julio wrote:
> Hi Ismael,
> 
> sfPing starts once the component is deployed and therefore it will
> check if the component is alive during sfDeploy and sfStart as well.
> This means that the components should not block on the sfDeploy and
> sfStart methods.

I see.

> The general rule is that any long operation (ex. starting a DB)
> started inside those methods should be processed in a separate thread
> to avoid liveness failures.

Makes sense.

> 
> To test if this is your case you can make liveness 0 (liveness =
> disabled)
> 
>   org.smartfrog.sfcore.processcompound.sfLivenessDelay=0
> 
> and see if your example now works.

It does indeed work.

> If this solves your problem please file a bug against the Jetty
> component and we will fix it for next release.

Done[1].

Regards,
Ismael

[1] http://jira.smartfrog.org/jira/browse/SFOS-676