Re: "received deploy request after it is terminated"

Steve,

This is in of itself perfectly possible and not an error. Any time after
the creation of the component (constructor and sfDeployWith) it may
terminate for some reason (e.g. liveness, some component terminating it,
etc) - and before it manages to notify its parent, the parent may ask it
to do the next phase of the lifecyle.

As to whether the initial termination after sfDeployWith is due to an SF
bug or not is a seperate issue.

Patrick


> I'm seeing this error on startup; sometimes intermittently, but right
> now always
>
> 2006/04/12 17:14:37:793 BST [ERROR][main] SFCORE_LOG - caught on
> deployment (HOST chamonix.hpl.hp.com:rootProcess:app)
> <SmartFrogDeploymentException: unnamed component. Component: HOST
> chamonix.hpl.hp.com:rootProcess:app received deploy request after it is
> terminated
>      reference: HOST chamonix.hpl.hp.com:rootProcess:app
>      primContext: included>
>          SmartFrogDeploymentException: unnamed component. Component:
> HOST chamonix.hpl.hp.com:rootProcess:app received deploy request after
> it is terminated, reference: HOST chamonix.hpl.hp.com:rootProcess:app,
> primContext: included
> 	at org.smartfrog.sfcore.prim.PrimImpl.sfDeploy(PrimImpl.java:771)
> 	at
> org.smartfrog.sfcore.compound.CompoundImpl.sfDeploy(CompoundImpl.java:483)
> 	at org.smartfrog.sfcore.common.ActionDeploy.Deploy(ActionDeploy.java:131)
> 	at
> org.smartfrog.sfcore.common.ActionDeploy.execute(ActionDeploy.java:210)
> 	at
> org.smartfrog.sfcore.common.ConfigurationAction.execute(ConfigurationAction.java:74)
> 	at
> org.smartfrog.sfcore.common.ConfigurationDescriptor.execute(ConfigurationDescriptor.java:856)
> 	at org.smartfrog.SFSystem.runConfigurationDescriptor(SFSystem.java:283)
> 	at org.smartfrog.SFSystem.runConfigurationDescriptor(SFSystem.java:263)
> 	at org.smartfrog.SFSystem.runConfigurationDescriptors(SFSystem.java:252)
> 	at org.smartfrog.SFSystem.runSmartFrog(SFSystem.java:450)
> 	at org.smartfrog.SFSystem.execute(SFSystem.java:344)
> 	at org.smartfrog.SFSystem.main(SFSystem.java:309)
>
> I'm assuming this is some kind of race condition. But maybe its some
> race condition in error handling, in which the underlying error is
> getting lost by this one that is engaging at cleanup.
>
> any thoughts?
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Smartfrog-developer mailing list
> Smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/smartfrog-developer
>




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642