Re: [certi-dev] Running Portico example under CERTI

[Eric Noulard]

2010/7/2 Roth, Christoph <address@hidden>:
>> What CERTI versions do you have installed on your machine? Which version?
>
> I use certi 3.3.3.
>
>> Did you use the prebuild CERTI binaries (rtia, rtig, libRTI), or do you
>> build CERTI on your own?
>
> I built certi on my own on a ubuntu linux machine: kernel 2.2.24-28, gcc 
> 4.2.4. I think there are some files missing in the archive you sent me 
> (especially the CMakeLists.txt) :)
>
> I also set the RTI_EXCEPTION=X now and changed the deleteObjectInstance 
> function. I get the following (for the federate that is initiated secondly), 
> so the reason is obviously before the deleteObjectInstance call:
>
> HLALOG - 1278078405.295837 - Federate - RTItypes.cc> RTI::Exception 
> [FederationExecutionAlreadyExists,0x0] - reason=
> HLALOG - 1278078405.296061 - Federate - RTItypes.cc> RTI::Exception 
> [FederationExecutionAlreadyExists,0x0] - reason=
> RTIA:: RTIA has thrown RTIinternalError exception.
> RTIA:: Reason: Unknown Message type received from RTIG.
> UN Socket(EmettreUN) : : Broken pipe
> HLALOG - 1278078405.316942 - Federate - RTItypes.cc> RTI::Exception 
> [RTIinternalError,0x0] - reason=NetworkError in tick() while sending 
> TICK_REQUEST: Error while sending UN message.
> terminate called after throwing an instance of 'RTI::RTIinternalError'
> RTI_EXCEPTION variable read, content = X
> Didn't create federation, it already existed
> Joined Federation as exampleFederate2
> Handles initialized
>
>
> RTIA: Statistics (processed messages)
> List of federate initiated services
> --------------------------------------------------
>       1 Message::JOIN_FEDERATION_EXECUTION (MSG#4)
>       1 Message::REGISTER_FEDERATION_SYNCHRONIZATION_POINT (MSG#6)
>       1 Message::GET_OBJECT_CLASS_HANDLE (MSG#112)
>       3 Message::GET_ATTRIBUTE_HANDLE (MSG#114)
>       1 Message::GET_INTERACTION_CLASS_HANDLE (MSG#116)
>       2 Message::GET_PARAMETER_HANDLE (MSG#118)
>
> List of RTI initiated services
> --------------------------------------------------
>       1 NetworkMessage::ANNOUNCE_SYNCHRONIZATION_POINT (MSG#13)
>      47 NetworkMessage::GET_FED_FILE (MSG#84)
>
>  Number of Federate messages : 9
>  Number of RTIG messages : 48
> *** W ** Removing temporary file _RTIA_8044_testfom.fed on RTIA stop.
> RTIA: Federate destroyed
>  TCP Socket  3 : total =      3706 Bytes sent
>  TCP Socket  3 : total =      5442 Bytes received
>  UDP Socket  5 : total =         0 Bytes sent
>  UDP Socket  5 : total =         0 Bytes received
>
>> The example seems to run just fine.
> Did you also try it using two federates?

Nope, and now that I did I face the same issue :-(
RTIA (RTIA_network.cc) does not handle some message
(NM_Register_Federation_Synchronization_Point)
sent by RTIG.

The truth is I don't really know [yet] how we could have lived with
that until now...

Could you open a bug report for that?
I'll try to handle it ASAP.

> For only one federate it also works on my machine. Do you think I should try 
> 3.4?

Yes and No.
No because I'm using 3.4 and the bug is there too.
Yes because 3.4 should be out in 2/3 weeks and giving it a try would
make it easier
to work in your case.
Furthermore 3.4 comes with a lot of enhancement and hopefully lesser bugs :-)

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org