I'll check running with tick() instead
of tick(min, max) and let you know tomorrow...
The 6th federate calls tick() and queryLTBS()
frequently and works like a charm...
Regarding PrettyDebug:
- I was waiting for log file redirection
to redirect the RTIA output the a certain file... You said you would try
to implement something..
- I tried RTIG_MSG=D
but that makes the federation execution very slow.. I think it may take
several hours to get to the point when the deadlock occurs....
Thanks,
Michael
Dipl.-Inform. Michael Raab
Fraunhofer-Institut für Fabrikbetrieb und -automatisierung IFF
Virtuell Interaktives Training
Sandtorstr. 22, 39106 Magdeburg, Germany
Telefon +49 (0) 391/ 40 90 122
Telefax +49 (0) 391/ 40 90 115
address@hidden http://www.iff.fraunhofer.de
oder http://www.vdtc.de
Von:
Eric Noulard <address@hidden>
An:
CERTI development discussions
<address@hidden>
Datum:
18.06.2012 15:55
Betreff:
Re: [certi-dev]
CERTI deadlock
Gesendet von:
address@hidden
2012/6/18 Michael Raab <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...
How does the 6th passive federate behave?
Did you try to patch PrettyDebug in order to get trace in a file and
enable traces
RTIA_TM=D
RTIA_MSG=D
RTIG_MSG=D
and may be add
RTI_EXCEPTION=D