70 likes | 189 Views
Termination Control. Termination Control. Termination Control. Target names and tags are looked up from the .properties files in the japc-svc-lookup directory: http://slwww.cern.ch/~pcrops/releaseinfo/pcropsdist/japc/ japc-svc-lookup/PRO/build/dist/japc-svc-lookup/
E N D
Termination Control Target names and tags are looked up from the .properties files in the japc-svc-lookup directory: http://slwww.cern.ch/~pcrops/releaseinfo/pcropsdist/japc/ japc-svc-lookup/PRO/build/dist/japc-svc-lookup/ The TC GUI sends a JMS message with “tag” as topic.
Termination Control The Termination Slave attached to the service listens for JMS messages and, upon reception, alerts the service operator that the countdown has been initiated. The operator may then delay the termination by the allotted time, or by portions of it.
Termination Control Once the time has elapsed, the Termination Slave runs a Courtesy Dialog and exits the service. The Courtesy Dialog has the purpose of informing an human operator, which may have been absent from the console, that the service has been terminated.
Termination Control Service main thread Service start Service restart Instantiate Termination Slave System.exit() Start countdown End countdown New process (operator) New process Courtesy Dialog JMS (through the network) Termination Control GUI
Termination Control To do: • implement module to recognize whether service is run standalone or from CCM • customize Slave module to fit service in order to have a “clean” termination, not just System.exit() • have Slave module report feedback to Termination Control (via JMS)