bugCERTI - Bugs: bug #50625, [3.5.1]request successed but...

 
 

bug #50625: [3.5.1]request successed but FederateNotExecutionMember excption throws

Submitted by:  None
Submitted on:  Fri 24 Mar 2017 09:22:35 AM UTC  
 
Category:  CERTI Severity:  3 - Normal
Item Group:  Software error Status:  Invalid
Privacy:  Public Assigned to:  JbCh <jb_ch>
Open/Closed:  Open Release:  3.5.0
Reproducibility:  Every Time Fixed Release:  NextRelease

Add a New Comment (Rich Markup)
   

You are not logged in

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

 

Tue 19 Jun 2018 02:19:42 PM UTC, comment #2:

Too long time before feedback.
Considering this one as invalid for release 4.0.0

JbCh <jb_ch>
Project AdministratorIn charge of this item.
Tue 19 Dec 2017 11:35:43 AM UTC, comment #1:

Hello,

Sorry for the late feedback. Can you please tell us more about this issue?

1) Did you try the behavior with latest release certi 3.5.1?
2) Can you provide a test case (C++ for example)?

Thanks,
Jb Ch

JbCh <jb_ch>
Project AdministratorIn charge of this item.
Fri 24 Mar 2017 09:22:35 AM UTC, original submission:

Use HLA1-3 interface
When use publishObjectClass method, FederateNotExecutionMember excption throws. It seems publish faild, but I can regitst and publish object right after this excption shows.
Try this steps:
1. join a federationExcutetion
2. publish object
3. resign federationExcutetion
4. join the same federationExcutetion
5. publish object -> FederateNotExecutionMember throws
6. regist a object that last step published ->success.

If did not do step 2, no excption throws.
Interaction have no problem.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jb_ch (Posted a comment)
  •  

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-19 jb_ch StatusNeed Info => Invalid
    2017-12-19 jb_ch Assigned toNone => jb_ch
    2017-12-19 jb_ch Severity6 - Security => 3 - Normal
        StatusNone => Need Info

    Back to the top


    Powered by Savane 3.4