bugCERTI - Bugs: bug #32904, ReserveObjectInsranceName method...

 
 

bug #32904: ReserveObjectInsranceName method call results in RTIA crash

Submitted by:  Eugene Chemeritskiy <tyz>
Submitted on:  Fri 25 Mar 2011 10:44:46 AM UTC  
 
Category: CERTISeverity: 3 - Normal
Item Group: Software errorStatus: Ready For Test
Privacy: PublicAssigned to: Eric NOULARD <erk>
Open/Closed: ClosedRelease: CVS
Reproducibility: Every TimeFixed Release: 3.4.1

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Fri 25 Mar 2011 09:11:08 PM UTC, comment #3:

Some more note.

The audit server has been largely unused for some time
so currently the rules for the appropriate "level"
is not well defined...

Concerning the queue.
CERTI has 3 queues:

TSO : for time stamped messages
FIFO : for RO messages
Command: for command-like message which correspond to
"functional" callback.

May be we should add some overall documentation in
the message specification file about that or even
common message field such that we can generate the
receive+classify in queue switch.

Eric NOULARD <erk>
Project AdministratorIn charge of this item.
Fri 25 Mar 2011 09:02:56 PM UTC, comment #2:

Hi again,

I've just checked a possible fix for this.
The fix includes your patch plus the move of
DataDistribution::reserveObjectName
to
ObjectManagement::reserveObjectName

because the method deserve to be there.
This makes me think that this new IEEE1516 service
has clearly been overlooked and/or nor
thoroughly tested.

Be prepared for other discovery in this area...
Nevertheless, thank you very much for the fix.

Eric NOULARD <erk>
Project AdministratorIn charge of this item.
Fri 25 Mar 2011 12:02:21 PM UTC, comment #1:

Hi Eugene,

Thank you for the patch.
I'll have a look soon and merge it if it's look fine.

I agree that the half-finished service things is strange...
may be this has been overlooked when merging some contribution.
I'll try to dig in the CVS history in order to check
whether if some other things may have been leftover at the same time.

Eric NOULARD <erk>
Project AdministratorIn charge of this item.
Fri 25 Mar 2011 10:44:46 AM UTC, original submission:

RTIA process crashes after the ReserveObjectInstanceName RTIAmbassador method call with the following output:

RTIA:: RTI has thrown RTIInternalError exception.
RTIA:: Reason: Unknown Message type <#> received from RTIG.

I discovered that both RTIG & RTIA processes did not handle messages corresponding to this service at all.
Taking into account the fact that I found the necessary functionality inside the sources, it is pretty strange.

I've made a patch, that solves the problem.
I cannot be sure that the chosen audit server level is correct and
that the reply messages are inserted into the correct queue on RTIA side.

Eugene Chemeritskiy <tyz>
Project Member

 

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

Attach File(s):
   
   
Comment:
   

Attached Files
file #23009:  reserveObjectInstanceName.patch added by tyz (2KiB - application/octet-stream)

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

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

     

     

    Follow 6 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 18 Oct 2011 08:38:24 PM UTCerkOpen/ClosedOpen=>Closed
      Fixed ReleaseCVS=>3.4.1
    Fri 25 Mar 2011 09:02:56 PM UTCerkStatusNone=>Ready For Test
      Fixed ReleaseUnknown=>CVS
    Fri 25 Mar 2011 12:02:21 PM UTCerkAssigned toNone=>erk
    Fri 25 Mar 2011 10:44:46 AM UTCtyzAttached File-=>Added reserveObjectInstanceName.patch, #23009

    Back to the top


    Powered by Savane 3.1-cleanup1