 |
MAK RTIspy API Documentation for HLA 4
|
All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
|
MAK RTIspy API Documentation for HLA 4
|
The rtiexec detects dropped TCP connections (via the RTI Forwarder DtTcpForwarderThread) and automatically resigns the federate.
When the DtTcpForwarderThread creates a TCP connection to the LRC, it sends a DtConnectMsg to it point-to-point without a forward to any other LRC. The DtConnectMsg assigns a unique ID to the LRC (across all federations). The member function DtExecFederateMgr::init() expects to process the DtConnectMsg if a reliable connection was created. The LRC uses this value to replace myID. If it does not get this message, myID reverts to its original value (either a random number or process ID (RTI_useRandomNumberForFedHandle)). So, even though the message is not received, the LRC should still be able to function (without fault tolerance based on lost TCP connections). A failure message is displayed if the DtConnectMsg is not received. This message is only a warning. To get rid of the warning message, the LRC would have to be directly fed a DtConnectMsg when the DtConnectMgr was created.
A DtDisconnectMsg sent to the rtiexec with the LRC ID causes that federate to be resigned from its federation.
The MAK RTI automatically resigns federates that fail to send heartbeat messages. You can disable this functionality in rid.mtl.
[<< Communicating with Remote LRCs and the rtiexec] [Home] [Finding Out when Data is Available to be Read >>]