I noticed a memory leak in my application using SSM.
When the "resetStateMachineReactively(...)" method is applied with currentState that contains a timer() in configuration,
(...withInternal().source(States.ORDERING_JOB).timer(30000).action(orderJob()).and()...)
it is started at the end of the method.
However, after the context is terminated, it will not be stopped. It continues to exist ad infinitum.
The triggered() method (in "ReactiveStateMachineExecutor") then always adds "TriggerQueueItem" to the "triggerSink" list,
which gradually keeps growing. (confirmed in java heap dump)
Hello SSM Team,
I noticed a memory leak in my application using SSM.
When the "resetStateMachineReactively(...)" method is applied with currentState that contains a timer() in configuration, (...withInternal().source(States.ORDERING_JOB).timer(30000).action(orderJob()).and()...) it is started at the end of the method.
However, after the context is terminated, it will not be stopped. It continues to exist ad infinitum.
The triggered() method (in "ReactiveStateMachineExecutor") then always adds "TriggerQueueItem" to the "triggerSink" list, which gradually keeps growing. (confirmed in java heap dump)
Thanks in advance