You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In decentralized execution, when STP(STAA) is set, the federation doesn't exit immediately after request_stop(). It waits until the STAA has passed and then exit.
...
server: 10
client: 11
server: 12
server done
DEBUG: RTI: Received message type 10 from federate 1.
DEBUG: RTI handling stop_request from federate 1.
LOG: RTI received from federate 1 a MSG_TYPE_STOP_REQUEST message with tag (0, 7).
LOG: RTI forwarded to federates MSG_TYPE_STOP_REQUEST with tag (0, 7).
DEBUG: RTI: Received message type 11 from federate 0.
LOG: RTI received from federate 0 STOP reply tag (0, 7).
LOG: RTI sent to federates MSG_TYPE_STOP_GRANTED with tag (0, 7)
client: 13
client done
DEBUG: Reading from socket 5 failed with error: `Resource temporarily unavailable`. Will try again.
DEBUG: Reading from socket 4 failed with error: `Resource temporarily unavailable`. Will try again.
DEBUG: Reading from socket 5 failed with error: `Resource temporarily unavailable`. Will try again.
...
When the STP is set to 10s, the federation exits in about ~10s. When it is set to a large value, the federation doesn't exit in reasonable time.
The text was updated successfully, but these errors were encountered:
In decentralized execution, when STP(STAA) is set, the federation doesn't exit immediately after
request_stop()
. It waits until the STAA has passed and then exit.Here's a minimal example to reproduce:
Output logs:
When the STP is set to 10s, the federation exits in about ~10s. When it is set to a large value, the federation doesn't exit in reasonable time.
The text was updated successfully, but these errors were encountered: