Actors with multiple pull input ports do not behave well in ET domain

[GoogleCodeExporter]

Issue reported by Irakli (DAWN).

What steps will reproduce the problem?
1. Create an actor inheriting from v5.Actor
2. Give it at least two blocking/pull input ports
3. Put it in a test model with a delay on one of the inputs

Expected behaviour :
 The actor should fire once every time a message has arrived on each input.

Actual behaviour :
 Run it in process/thread-based model : behaves ok
 Run it in the event-based ET model : the actor is fired twice,
once for every input that was received separately...

Cfr attached unit test to reproduce the problem.

Original issue reported on code.google.com by erwin...@gmail.com on 4 Feb 2014 at 1:28

Attachments:

• Simple2BlockingPortActorTest.java

[GoogleCodeExporter]

Fixed in ...v5.Actor.doPreFire().
Committed on trunk, branch v8.5, branch for dawn & on DAWN github

Original comment by erwin...@gmail.com on 6 Feb 2014 at 8:02

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by erwin...@gmail.com on 5 May 2014 at 2:45

• Changed state: Verified