Re: How to see SF errors

Andreas, 

I think the problem that you have is due to the way you deploy your
description.

When deploying a description, the command sfStart will not return until
the sfStart lifecycle method of the root component of your description
has completed. If this component is deploying Parallel components, then
it will almost return immediately, and the shell script won't receive
more notifications about the lifecycle of that application, because
parallel has its own thread to drive the sfStart lifecycle of its
children.

If you want to continue receiving notifications you can do several
things: 
a) build a root component for your application that is capable of
sending notifications when something happens, you can even use the
lifecycle hooks (see trace component for an example) and this component
could use, for example, the jabber component to send notifications to a
central server, email, or multicast.

b) add components to your description to send notifications about the
progress of the system. For an example check how the dynamic web server
example sends notifications about the installation steps.

C) you can register your new application as a child of a component which
mission is to receive notifications and liveness events of its children
and then react to it (raise alarms, send events, emails, ...) If you use
the command line to deploy your description, then you can register your
new application with your special compound using the following syntax:

smartfrog -a "HOST
localhost:sfDefault:Andreas":DEPLOY:org/smartfrog/examples/counter/examp
le.sf::localhost:
-e

This will deploy counter component called "Andreas" as a child of
localhost:sfDefault. Note that sfDefault has to be capable of having
children.


Julio

> -----Original Message-----
> From: smartfrog-support-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:smartfrog-
> support-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Andreas
Unterkircher
> Sent: 15 November 2006 08:04
> To: smartfrog-support
> Subject: [Smartfrog-support] How to see SF errors
> 
> 
> Hello,
> 
> We're running the SF deamon (as a service, no gui) on several
machines.
> There logging is configured like
> 
>
org.smartfrog.sfcore.logging.LogImpl.loggerClass=org.smartfrog.sfcore.lo
gg
> ing.LogToFileImpl
> 
> We always deploy on one host hostA a description that has
subcomponents
> that get deployed to other hosts (with sfProcessHost hostB etc.). The
> problem is that if I deploy such a description from my machine with
> 
> sfStart hostA ...
> 
> if there is any error in deployment I don't see it on my machine, but
I
> have to look into the log file on hostA or even into log file of the
> host the subcomponent got deployed to with sfProcessHost (it seems to
me
> that the errors encountered get also logged on hostA, but I'm not sure
> if this is always the case). Now the question:
> Is it possible to propagate these errors back to my machine so that I
> see it in my local terminal where I typed "sfStart..." ?
> 
> Thanks,
> Andreas
> 
> 
>
------------------------------------------------------------------------
-
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to
share
> your
> opinions on IT & business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
> _______________________________________________
> Smartfrog-support mailing list
> Smartfrog-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/smartfrog-support

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV