The scheduler incorrectly maintains it's 'Started' state

Tony Sheehy 9 years ago updated by anonymous 5 years ago 3

If the Event Broker scheduler is in a 'Started' state, and it becomes unlicensed, the scheduler will maintain this state until the service is restarted

{ Which provides a set of licensed functionality to unlicensed customers }


To reproduce this behaviour:

1. Start the EventBroker service
2. Ensure that the scheduler has started
3. Add a license that expired before the day of reading.
4. Ensure that the Event Broker instance is now unlicensed and that the scheduler has maintained this state.

Reassigned for confirmation of completion.

Apologies Tony, the issue was originally yours. I should have resolved it to have you close it.