[
https://issues.apache.org/jira/browse/UIMA-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Challenger resolved UIMA-3831.
----------------------------------
Resolution: Fixed
Ref start was forgetting to check ServiceSet to see if things had halted
because of excessive errors. As well, the excessive-errors flags need to be
reset on --modify or --start. As well, initialization errors weren't being
completely reflected back to the .meta and the user.
> SM keeps trying to start a service if its initialization fails in a special
> way
> -------------------------------------------------------------------------------
>
> Key: UIMA-3831
> URL: https://issues.apache.org/jira/browse/UIMA-3831
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Affects Versions: 1.0.0-Ducc
> Reporter: Burn Lewis
> Assignee: Jim Challenger
> Priority: Minor
> Fix For: 1.1.0-Ducc
>
>
> SM seems to know it failed but will attempt to restart forever if left alone!
> service log: /users/burn/2014-exp13/watsonmd/try3/logs/S-1405/12844
> java.lang.ClassNotFoundException: org.apache.http.message.AbstractHttpMessage
> ducc.log:
> rationale: process initialization failure(s) occurred
> SM.log:
> 16 May 2014 22:11:59,788 WARN SM.ServiceSet - signalUpdate 1405 Instance
> 12844 Excessive initialization failures. Total failures[1] allowed [1], not
> restarting.
> ....
> 16 May 2014 22:11:59,792 INFO SM.ServiceSet - start 1405 Starting
> instance 0
> ...
> 16 May 2014 22:12:01,617 INFO SM.ServiceInstance - start 1405 START
> INSTANCE COMPLETE
> 16 May 2014 22:12:01,617 INFO SM.ServiceSet - start 1405 Instance[ 0 ] id
> 12845
--
This message was sent by Atlassian JIRA
(v6.2#6252)
