Inserting RTI::RTIambassador::enableAsynchronousDelivery()
before object and interaction registration (but after time dependencies)
made no difference.
At the moment its hard for me to place
the call between federation creation/joining and declaration of time dependencies.
Do you think that step may help?
Michael
Dipl.-Inf. 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:
11/08/2010 03:05 PM
Betreff:
Re: [certi-dev]
Federation startup crash
Gesendet von:
address@hidden
2010/11/8 Michael Raab <address@hidden>:
> Thanks!
>
> Unfortunately I cannot provide any example as we have CERTI calls
integrated
> into some other libraries. Sorry.
> BTW: I'm using Windows XP 32bit.
>
> Hope to hear from you soon, as our timeframe is tight. :-(
Could you try to add a call to:
RTI::RTIambassador::enableAsynchronousDelivery()
before ANY register or publish.
The default behavior of CERTI is to NOT deliver asynchroneously, which
means
(among other thing) that you cannot receive an RO message while you
are in Time Advance state.
DiscoverObject is an RO message.
So DiscoverObject may be delayed until you get TAG.
There is a [distributed] race condition because you should'nt receive an
RAV for
an object you did not discover yet but enabling asynchronous delivery should
"fix" the issue.
Could you try that while I'm working on a "real" fix.
--
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org