-
Key: DSS2-79
-
Legacy Issue Number: 5188
-
Status: closed
-
Source: MITRE ( Ms. Susan Symington)
-
Summary:
When a federate is in the Federate Restore In Progress state, the identity of that federate, being in a possible state of flux, is undefined. When at least one federate in the federation execution is in the Federate Restore In Progress state, it does not make sense for the RTI to maintain the values of instance attributes of HLAmanager.HLAfederate object instances, because it is not clear to which federate any given HLAmanager.HLAfederate object instance corresponds, nor is it clear at which federate an update to such an instance attribute should be reflected. So, while under normal circumstances, if a service invocation occurs that causes the HLAfederateState of a HLAmanager.HLAfederate object instance to change value, then the corresponding instance attribute should be updated, there is an exception to this rule. The state of each HLAmanger.HLAfederate object instance is in flux during a restore. Only after all federates have restored successfully and moved back into the Active Federate state should the RTI resume maintaining the values of instance attributes of HLAmanager.HLAfederate object instances. Therefore, it is recommended that the text be amended to make clear that when a federate's state changes from that of Active Federate to that of Federate Restore In Progress, no updates are expected. In fact, the MOM is not expected to update any instance attribute values after the first Federation Restore Begun callback is invoked at any federate in the federation execution and before the last Federation Restored callback is invoked at some federate for a given federation restoration.
-
Reported: DSS 1.1 — Wed, 10 Apr 2002 04:00 GMT
-
Disposition: Resolved — DSS 2.0
-
Disposition Summary:
see above
-
Updated: Fri, 6 Mar 2015 20:58 GMT
DSS2 — Table 6: MOM attribute table: HLAfederateState
- Key: DSS2-79
- OMG Task Force: Distributed Simulation V2.0 FTF