oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Foster <holeno...@me.com>
Subject Re: PushPull DaemonLauncher
Date Thu, 21 Nov 2013 21:43:46 GMT
Hey Jordan,

Try not specifying the <runInfo> element for your daemons in RemoteSpecs.xml file.  It
should just run once through for those sites.  I believe the pushpull shuts down automatically
when all deamons have terminated, so after you run one pass it should just terminate.  It's
been a while since i've worked with push-pull code, if that doesn't work i'll have to dig
further into the code.

if you looking to do just a on off download a given file, then you might consider just using
cas-protocol directly.  Take a look at: https://svn.apache.org/repos/asf/oodt/trunk/protocol/api/src/main/resources/policy/cmd-line-actions.xml.
 You can run cas-protocol via this bin script: https://svn.apache.org/repos/asf/oodt/trunk/protocol/api/src/main/bin/protocol.
 Just build and deploy like all other cas products and that script will end up in the bin
directory.  If you would like to add custom action to cas-protocol there is documentation
for this at: https://svn.apache.org/repos/asf/oodt/trunk/cli/README.txt


On Nov 07, 2013, at 05:31 PM, Jordan Padams <jordan.padams@gmail.com> wrote:

Hello all,

I am trying to develop a pretty simple wrapper for the PushPull where I
call the DaemonLauncher to run through the daemons in my config once and
then shut down altogether. We currently don't have a need to have the
software running at intervals.

On that note, here are a few of the methods I've tried but haven't worked:

1. DaemonLauncher.main() - The software hangs because of the wait() waiting
for a notify().
2. DaemonLauncher.viewDaemonWaitingList() - I've tried monitoring the
daemon waiting list, and quit() the DaemonLauncher once it gets to 0, but
then it misses the last daemon in my config.

Is there a way for me to wait on the DaemonLauncher until all daemons have
completed, then quit?

I've implemented a quick workaround by creating the following method so I
can see if daemons are still running:

public boolean hasRunningDaemons() {

return this.dm.hasRunningDaemons();

I don't have a lot of experience with daemon processes so this may just be
something I'm blatantly missing. Appreciate the help.


Jordan Padams
Software Engineer
NASA Jet Propulsion Laboratory

  • Unnamed multipart/alternative (inline, None, 0 bytes)
    • Unnamed multipart/related (inline, None, 0 bytes)
View raw message