It was detected that the event state is not working as expected when we have multiple events and the exclusive = true (the by default setting)

Case event_state_multiple_end:

1) Create an instance of the event_state_multiple_end SW

    
The following sysout is shown "event_state_multiple_end: bc6ecef7-9f53-41f5-afd7-85497b2b5176 has started."

2) Send the "event3" to the given instance as shown in the picture

The following sysout is shown: "event_state_multiple_end: bc6ecef7-9f53-41f5-afd7-85497b2b5176 event3 has arrived.", as expected.

3) However the process instance is still alive, which is bad, since by default we have exclusion = true. (use the get query to verify)

Case event_state_multiple_end_exclusive_false:

This SW looks to work work, i.e., the process waits for all the events, an then finishes.

Case event_state_multiple_transition:

1) Create an instance of the event_state_multiple_transition SW

The following sysout is shown: "event_state_multiple_transition: 2e8ae086-2127-40b1-8a0f-ea4e52e85439 has started.", as expected.

2) Send the "event3" to the given instance.

The following sysout is show: 
    "event_state_multiple_transition: 2e8ae086-2127-40b1-8a0f-ea4e52e85439 event3 has arrived.", as expected.

    "event_state_multiple_transition: 2e8ae086-2127-40b1-8a0f-ea4e52e85439 has finished.", as expected.

3) However the process instance is still alive, which is bad, since by default we have exclusion = true. (use the get query)

Case event_state_multiple_transition_exclusive_false:

This SW looks to work work, i.e., the process waits for all the events, an then finishes.

Attached goes the SW, and the reproducer can be found here.

https://github.com/wmedvede/event-sate-timeouts-analysis