Answers to: Ivy WorkflowSystemEvent was not fired when session timeout?

Comment by vinh_ on Reguel Wermelinger's answer

vinh_ — Wed, 15 May 2019 10:30:11 -0400

You are correct about the EnvironmentNotAvaiableException we are using BusinessRepo in the Listener, it seem out of scope of the dependency injection, in Axon.ivy 7.0.8, the error is not show in the Runtime Log, but in the Error windows. The good news is when we upgrade to 7.0.11, the issue has gone.

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Thu, 25 Apr 2019 03:22:06 -0400

It could be that your listener registration is done after states have already been reseted. Can you share how you register for the event? Via programmed start event bean or with an IServerExtension?

Comment by vinh_ on Reguel Wermelinger's answer

vinh_ — Wed, 24 Apr 2019 23:13:39 -0400

I just found a case may cause this issue, when I restart the Ivy Engine, is the event also fired?

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Wed, 24 Apr 2019 10:41:40 -0400

I tested it with 7.3.1 ... but I do not expect a significant change in this area between 7.0.X and 7.3

Comment by vinh_ on Reguel Wermelinger's answer

vinh_ — Tue, 23 Apr 2019 23:34:59 -0400

I will check it again, I could manage the EnvironmentNotAvailableException, but in my case the Event was not fired at all. Did you check with Ivy Engine 7.0.8 Linux version.

Answer by Reguel Wermelinger

Reguel Wermelinger — Tue, 23 Apr 2019 03:57:53 -0400

I can reproduce that the task state event is fired also on session timeouts. However, I see that in this case chances are pretty high that you face an EnvironmentNotAvailableException as many ivy APIs rely on a running Session, ProcessModelVersion and Task. Could it be that you have the same exceptions in your logs and therefore your listener code was not really executed?