Event fired against wrong state machine when FSMs collaborate about squirrel HOT 3 CLOSED

Hi Jeremy,

Thanks for your investigation. The problem was fixed by adding a configuration option (isDelegatorModeEnabled) which default value is false. The provided test case has also been added to the project. I deployed a snapshot version 0.3.2-SNAPSHOT to the maven repo. You can have a try first. If everything works fine for you, I will release this version soon.

One more thing about this collaborate use case is sometimes dead lock may happened if locking order was not forced the same, e.g. while fsmA is processing a event, it needs to read fsmB's current state. However, fsmB is also processing a event and also need to read fsmA's current state.

Henry

from squirrel.

Many thanks, Henry. That fixes it.

BTW: Dead-lock does not affect us because our test is single-threaded. Although I said (for simplicity but somewhat misleadingly) we were using input and output streams, actually the test uses a simple interface that synchronously receives bytes passed from one FSM to the other.

Thanks again,
Jeremy

from squirrel.

Great! I will release it later. Only contain this fix.

from squirrel.