I got some additional log information
and it seems that the fifth federate is blocked by the tick call after
NER.
Thanks,
Michael
Von:
Michael Raab <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
18.06.2012 12:13
Betreff:
Re: [certi-dev]
CERTI deadlock
Gesendet von:
address@hidden
Hi Eric,
just a quick update on that....
It looks like 4 federates have called NER and are ticking actively, waiting
for the TAG...
The fifth federate seems to be blocked within the NER call...
Hope this helps,
Michael
Von: Eric
Noulard <address@hidden>
An: CERTI
development discussions <address@hidden>
Datum: 15.06.2012
13:01
Betreff: Re:
[certi-dev] CERTI deadlock
Gesendet von: address@hidden
2012/6/15 Michael Raab <address@hidden>:
> Eric,
>
> of course I'm calling tick until the appropriate grants arrive....
>
> Attached to this mail you can find the latest debug outputs of the
federates
> before the deadlock occurs.
> Apparently all of them are waiting for a TAG.
I really need to know "how" it freeze.
Could you tell me if the federate are blocked "in a livelock"
or blocked on some RTIA call.
Mainly are they (all) ticking actively or are they (some or all)
blocked *inside* a tick call ?