You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2016/05/06 19:58:12 UTC
[jira] [Closed] (UIMA-4656) Start & stop & check scripts don't
handle the broker the same as other daemons
[ https://issues.apache.org/jira/browse/UIMA-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis closed UIMA-4656.
----------------------------
Resolution: Fixed
Broker & database now recognized & handled by scripts
> Start & stop & check scripts don't handle the broker the same as other daemons
> ------------------------------------------------------------------------------
>
> Key: UIMA-4656
> URL: https://issues.apache.org/jira/browse/UIMA-4656
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Burn Lewis
> Assignee: Burn Lewis
> Priority: Minor
> Fix For: 2.1.0-Ducc
>
>
> Using the -c option the broker can be started, but not stopped.
> It suggests refreshing the pids with check_ducc but the -p option is needed.
> check_ducc doesn't recognize it (ducc unknown-java).
> check_ducc -k doesn't kill it - perhaps because it is the only daemon around?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)