You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org> on 2012/03/20 23:43:49 UTC

[jira] [Commented] (OOZIE-771) oozied.sh should exec catalina.sh instead of forking it off

    [ https://issues.apache.org/jira/browse/OOZIE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233899#comment-13233899 ] 

jiraposter@reviews.apache.org commented on OOZIE-771:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4422/
-----------------------------------------------------------

Review request for oozie.


Summary
-------

trivial patch


This addresses bug OOZIE-771.
    https://issues.apache.org/jira/browse/OOZIE-771


Diffs
-----

  trunk/distro/src/main/bin/oozied.sh 1303178 

Diff: https://reviews.apache.org/r/4422/diff


Testing
-------

local build/run


Thanks,

Roman


                
> oozied.sh should exec catalina.sh instead of forking it off
> -----------------------------------------------------------
>
>                 Key: OOZIE-771
>                 URL: https://issues.apache.org/jira/browse/OOZIE-771
>             Project: Oozie
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.2.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 3.2.0
>
>         Attachments: OOZIE-771.patch.txt
>
>
> In Bigtop we would like to start supporting constant monitoring of the running daemons (BIGTOP-263). It would be nice if Oozie can support that requirement by execing Catalina instead of forking it off. Currently we have to track down the actual process being monitored through the script that still hangs around.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira