You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2013/05/18 13:09:15 UTC
[jira] [Resolved] (UIMA-2918) Webserver support for ping-only
services
[ https://issues.apache.org/jira/browse/UIMA-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lou DeGenaro resolved UIMA-2918.
--------------------------------
Resolution: Fixed
Code delivered.
> Webserver support for ping-only services
> ----------------------------------------
>
> Key: UIMA-2918
> URL: https://issues.apache.org/jira/browse/UIMA-2918
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Fix For: 1.0-Ducc
>
>
> 1. Service health for all services should be good/poor (again!) not up/down
> 2. ping-only services should have blanks for instance, deployments, size
> 3. ping-only services should have [ping-only] for class
> 4. ping-only start/stop buttons enabling controlled by (new!) meta.ping-only and meta.is-started
> deprecated:
> /** * A service is startable if it's UIMA-AS, or if it's CUSTOM and has a process_executable * associated with it. A non-startable CUSTOM service may have only a pinger. */ boolean isStartable() { switch ( service_type ) { case UimaAs: return true; case Custom: return job_props.containsKey("process_executable"); } return false; // redundant but needed for compilation } if that returns false it's ping-only
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira