[certi-dev] Federation startup crash

[Michael Raab]

Hi all,

I have again problems with CERTI. This
time the start up of my federation crashes. For testing purposes I have
only two federates. 
The start up procedures look like this:

FED1:
RTIAmb: calling createFederationExecution
RTIAmb: calling joinFederationExecution.
RTIAmb: calling enableTimeConstrained.
FedAmb: 0.000000 timeConstrainedEnabled
callback received.
RTIAmb: 0.000000 calling enableTimeRegulation.
FedAmb: 60.000000 timeRegulationEnabled
callback received.
RTIAmb: calling queryFederateTime.
RTIAmb: calling queryLookahead.
RTIAmb: calling queryFederateTime.
RTIAmb: calling publishObjectClass.
RTIAmb: calling registerObjectInstance.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling subscribeObjectClassAttributes.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.

FED2:
RTIAmb: calling createFederationExecution
RTIAmb: calling joinFederationExecution.
RTIAmb: calling enableTimeConstrained.
FedAmb: 0.000000 timeConstrainedEnabled
callback received.
RTIAmb: 0.000000 calling enableTimeRegulation.
FedAmb: 60.000000 timeRegulationEnabled
callback received.
RTIAmb: calling queryFederateTime.
RTIAmb: calling queryLookahead.
RTIAmb: calling queryFederateTime.
RTIAmb: calling publishObjectClass.
RTIAmb: calling registerObjectInstance.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: calling subscribeInteractionClass.
RTIAmb: calling subscribeInteractionClass.
RTIAmb: calling subscribeInteractionClass.
RTIAmb: calling publishObjectClass.
RTIAmb: calling registerObjectInstance.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: calling publishObjectClass.
RTIAmb: calling registerObjectInstance.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: calling publishObjectClass.
RTIAmb: calling registerObjectInstance.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: calling publishInteractionClass.
RTIAmb: 60.000000 calling updateAttributeValues.
RTIAmb: 60.000000 calling updateAttributeValues.

They get started both in sync, each
federate waits for my reaction (with a MessageBox :-)) after line 7 (queryFederateTime),
to be sure that none of them advances time before the other has joined
and configured. This worked well with DMSO RTI for several years.
After I permit advancement for both,
Federate 1 throws an exception during the process of publishment of one
of its interaction classes. But not always for the same interaction class
:-(. Apparently the errors occurs during getParamterHandle() function call.
The Exception message is: libRTI: Network Read Error waiting RTI reply.
Has someone an idea what may cause this
behaviour?

FYI:  I'm using 3.3.3cvs

Thanks & Best regards,
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