Bug in alarmerwatchthread
Looks like the alarmer watch thread can fire the transition to RunningDegraded while the FM is in state configured. From the logs:
2019-07-29 14:55:54 and 766 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
INFO [SethLog HCAL HCAL_LEVEL_1] 3 calcState = Configured, from state (actualState): Configuredfor FM: http://cmsrc-hcal.cms:16000/urn:rcms-fm:fullpath=/hcalpro/Local/HBHE_May14-19,group=HCAL_LEVEL_1,owner=hcalpro
2019-07-29 14:56:41 and 619 ms : cms.hcalpro.rcms.fm.app.level1.HCALEventHandler
ERROR [HCAL HCAL_LEVEL_1] Error! Got an exception: AlarmerWatchThread()...
Here is the exception: Failed to send a SOAP command, ParameterQuery, to http://hcalmon.cms:9945.
...going to change to RUNNINGDEGRADED state
2019-07-29 14:56:41 and 620 ms : cms.hcalpro.rcms.statemachine.StateMachineEngine
ERROR Transition for input SetRunningDegraded and State Configured not defined
2019-07-29 14:56:41 and 621 ms : cms.hcalpro.rcms.fm.fw.EventProcessor
ERROR State Machine error for Input SetRunningDegraded
2019-07-29 14:56:41 and 624 ms : cms.hcalpro.rcms.fm.fw.FunctionManager
ERROR Function Manager executeEvent: event processing failure
2019-07-29 14:56:41 and 624 ms : cms.hcalpro.rcms.fm.fw.FunctionManager
ERROR execution of event class rcms.statemachine.definition.Input failed
Review how and when we fire the SetRunningDegraded event.