bugCERTI - Bugs: bug #23746, RTIG should detect RTIA crash and...

 
 

bug #23746: RTIG should detect RTIA crash and destroy its object instances

Submitted by:  Petr Gotthard <gotthardp>
Submitted on:  Tue 01 Jul 2008 08:06:54 PM UTC  
 
Category: CERTISeverity: 4 - Important
Item Group: Software errorStatus: None
Privacy: PublicAssigned to: None
Open/Closed: OpenRelease: 3.3.0
Reproducibility: NoneFixed Release: Unknown

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Wed 02 Jul 2008 08:46:35 AM UTC, comment #3:

I know that RTIA-RTIG is out of scope because it's
a specific design choice, but I think may be there
could be some rationale about expected behavior if
a federate

1- unexpectedly quit the federation
2- resign from federation without unpublishing/deleting Object
first

In the resign case, we have some indication
see 4.5 (HLA 1.3 document)

Resign Federation Execution service shall accept an action argument that directs the RTI to perform zero or more of the following actions:
— Release all owned instance attributes for future ownership acquisition. This shall place the instance attributes
into an unowned state (implying that their values are not being updated), which shall make them eligible for
ownership by another federate. See Clause 7., Ownership management for a more detailed description.
— Delete all object instances for which the federate has that privilege (implied invocation of the Delete Object
Instance service).

So a Federate may voluntarily resign from federation
without deleting object instance or even set instance
attribute to unowned.

I think this would lead to the same state as the crash case?

This does not give us the answer but, I don't really know
what we should do in case of crash.

Eric NOULARD <erk>
Project Administrator
Wed 02 Jul 2008 08:30:35 AM UTC, comment #2:

The RTIA-RTIG communication is not in the scope of the HLA standards, so even failures of the RTIA-RTIG communication are probably also out of scope. I don't expect it's described in the standards. (After a quick search in IEEE 1516 I haven't found anything.)

Petr Gotthard <gotthardp>
Project Member
Wed 02 Jul 2008 08:16:28 AM UTC, comment #1:

I don't know if we clearly thought
about 'failure' mode in CERTI.

Did you read something about failure secnarii
in HLA documents?

I add Pierre as cc for comment.

Eric NOULARD <erk>
Project Administrator
Tue 01 Jul 2008 08:06:54 PM UTC, original submission:

When a federate/RTIA crashes, the published objects remain in the RTIG, so the next simulation run throws an exception. This causes a lot of inconvenience in unstable environments.

Is there a reason why RTIG should not destroy all objects owned by an RTIA that just has disconnected/crashed without unpublishing? (I think that ownership management should "assure" that after a given RTIA crashes, no one will ever be able to change/destroy its object instances.)

Petr Gotthard <gotthardp>
Project Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Digest:
   bug dependencies.

 

Carbon-Copy List
  • -unavailable- added by erk (Posted a comment)
  • -unavailable- added by erk (Needs comments)
  • -unavailable- added by gotthardp (Submitted the item)
  • -unavailable- added by gotthardp
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 02 Jul 2008 05:10:04 PM UTCerkDependencies-=>bugs #23725 is dependent
    Wed 02 Jul 2008 08:16:28 AM UTCerkCarbon-Copy-=>Added siron
    Tue 01 Jul 2008 08:06:54 PM UTCgotthardpCarbon-Copy-=>Added -unavailable-

    Back to the top


    Powered by Savane 3.1-cleanup1