[
https://issues.apache.org/jira/browse/UIMA-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Challenger updated UIMA-2919:
---------------------------------
Description:
Ping-only services don't have service instances. The autostart logic works by
comparing declared instances to started instances and starting new instances to
match the declared number.
Since ping-only services have no instances, autostart never starts anything!
Must take into account ping-only in the autostart logic.
Related, and found in the same debugging session, the (old, temporary, to cope
with AMQ OOM issues) timer to kick off CUSTOM pings needs to be switched to the
proper timer as used by the internal UIMA-AS pinger.
Further - it is hard for the web server to know what is going on with a
ping-only service because there are not active instances. The Service Manger
will start placing state into its meta properties file to indicate whether the
pinger is active or not : meta.ping-active and whether the service is in fact a
ping-only service: meta.ping-only = true
was:
Ping-only services don't have service instances. The autostart logic works by
comparing declared instances to started instances and starting new instances to
match the declared number.
Since ping-only services have no instances, autostart never starts anything!
Must take into account ping-only in the autostart logic.
Related, and found in the same debugging session, the (old, temporary, to cope
with AMQ OOM issues) timer to kick off CUSTOM pings needs to be switched to the
proper timer as used by the internal UIMA-AS pinger.
> DUCC Service Manager incorrect handling of autostart for ping-only services
> ---------------------------------------------------------------------------
>
> Key: UIMA-2919
> URL: https://issues.apache.org/jira/browse/UIMA-2919
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jim Challenger
> Assignee: Jim Challenger
> Fix For: 1.0-Ducc
>
>
> Ping-only services don't have service instances. The autostart logic works
> by comparing declared instances to started instances and starting new
> instances to match the declared number.
> Since ping-only services have no instances, autostart never starts anything!
> Must take into account ping-only in the autostart logic.
> Related, and found in the same debugging session, the (old, temporary, to
> cope with AMQ OOM issues) timer to kick off CUSTOM pings needs to be switched
> to the proper timer as used by the internal UIMA-AS pinger.
> Further - it is hard for the web server to know what is going on with a
> ping-only service because there are not active instances. The Service Manger
> will start placing state into its meta properties file to indicate whether
> the pinger is active or not : meta.ping-active and whether the service is in
> fact a ping-only service: meta.ping-only = true
--
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
