You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like when machine is stopped then TimerTrigger is not stopped which effectively keeps it armed and trigger will fire causing new queued events to get spooled in a DefaultStateMachineExecutor.
The text was updated successfully, but these errors were encountered:
- Trying to handle scenario where TimerTrigger keeps firing
even if machine is stopped or has moved away from its
hosting state.
- Explicitely handle trigger starts/stops in
DefaultStateMachineExecutor when executor itself
is started/stopped.
- Fixesspring-projects#321
- Trying to handle scenario where TimerTrigger keeps firing
even if machine is stopped or has moved away from its
hosting state.
- Explicitely handle trigger starts/stops in
DefaultStateMachineExecutor when executor itself
is started/stopped.
- Backport #321
- Relates to #307
It looks like when machine is stopped then
TimerTrigger
is not stopped which effectively keeps it armed and trigger will fire causing new queued events to get spooled in aDefaultStateMachineExecutor
.The text was updated successfully, but these errors were encountered: