certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Fwd: Unsubscribing objectclasses on run causes problems


From: Timi Tuohenmaa
Subject: Re: [certi-dev] Fwd: Unsubscribing objectclasses on run causes problems
Date: Tue, 17 Dec 2013 10:00:42 +0200

Hi,

I use older HLA 1.3 interface where named objects are not reserved and
they are freed when object is deleted. Other federates see object name
as free since they did not stop subscribing object class.

Unsubscribing to object class should probably clear local list of used
names if there is one.

Kind regards,
Timi

2013/12/16 Stefan Puch <address@hidden>:
> Hi Timi,
>
> are you using CERTI  with HLA 1.3 or HLA 1516? If you are using the latter you
> should take a look at link below concerning the HLA implementation status.
>
> When using named objects in HLA 1516 (regarding the standard) it is necessary 
> to
> reserve and release an instance name of an object at RTI before registering /
> removing an object instance at RTI. That a federate registers an object 
> instance
> is required if another federate (that subscribed to that object class) will be
> able to discover an instance.
> Looking into the document you can see, that "Release Object Instance Name" is
> not jet implemented (if document is up to date, because I didn't take a look
> into the source code), so an reserved name be reserved until the federation is
> destroyed. Maybe this explains your observed problem.
>
> http://cvs.savannah.gnu.org/viewvc/certi/doc/CERTI-HLA-ImplementationStatusList.ods?root=certi&view=log
>
> Kind regards
> Stefan
>
> Am 16.12.2013 14:54, schrieb Timi Tuohenmaa:
>> Hi,
>>
>> I just noticed a problem when some federate executes unsubscribe to
>> objectclass that it has had subscribed earlier.
>>
>> If that objectclass had named objects when unsubscribe were executed
>> it never heard that object was removed and therefore thinks that
>> selected name was still reserved for later use.
>>
>> Interestingly creating object with such (mistakenly) reserved name
>> causes creation of such object to federation but that single federate
>> thinks create failed.
>>
>> I had pretty complex program where I noticed this, but from logs it
>> looked like it missed removes even internally. Obviously I can't be
>> sure if this was exactly the problem behind, but it helped that I
>> changed logic that program only unsubscribed on quit.
>>
>> (using new 3.4.2, but problem existed in 3.4.1 too)
>>
>> Kind regards,
>> Timi Tuohenmaa
>>
>> (note! I already sent this, but I wonder if it actually ended to
>> post-list as I send address was something I did not use when I
>> subscribed. Also nobody answered)
>>
>
> --
> +--------------------------------+---------------------------------+
> | Dipl.-Inform. Stefan Puch   <Master degree in computer science>  |
> +--------------------------------+---------------------------------+
> | C.v.O. Universität Oldenburg   | C.v.O. University of Oldenburg  |
> | Department für Informatik      | Department of Computer Science  |
> | Abteilung Hybride Systeme      | Research Group Hybrid Systems   |
> | Escherweg 2, 26121 Oldenburg   | Escherweg 2, D-26121 Oldenburg  |
> |                                |                                 |
> | Telefon: +49 441 9722-564      | Phone: +49 441 9722-564         |
> | Fax:     +49 441 9722-502      | Fax:   +49 441 9722-502         |
> +--------------------------------+---------------------------------+
>
>
> --
> CERTI-Devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/certi-devel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]