0
Completed

Event Broker does not retain state of scheduler on service restart

Bob Bradley 7 years ago • updated by anonymous 3 years ago 6

From DEEWR-33:

Operational problems are caused by the present behaviour whereby the Event Broker scheduler ALWAYS starts when the Event Broker service is restarted (either explicitly or on a server reboot). This has caused a number of problems over the past week, and we are being forced to disable the Event Broker service while performing some FIM data reload scenarios. This is a usability issue ... and more of a problem in a production/migration scenario than say in DEV.

The following page should be deleted following completion of this issue:
EB31:Issues with FIM Event Broker Scheduler starting following a service restart

For v3.0.0, I have updated the following pages of the documentation:

This should mitigate any potential issues encountered with this behaviour until this feature has been implemented.

Reassigned for confirmation of completion, in separate EB-426 branch.

Started state is persisted but stopped is not; (service tries to start scheduler if stopped)

If SchedulerState.Started the Scheduler won't be enabled and schedules won't be fired.

Reassigned for confirmation of completion.

Now that studio doesn't run a check for the status immediately after an async call, this can be closed.