The connector job ChangeDetectionSchedulerJobDecorator could not be run as the Chris21 Person Connector is currently disabled
Matthew Woolnough 11 years ago • updated by anonymous 8 years ago • 2
The following exception was being logged constantly in Matt's environment:
20121028,00:00:21,UNIFY Identity Broker,Void <.ctor>b__0(),Error,"An exception has occured whilst performing a job for partition 34b83581-377c-41b5-afb9-2a705076285f job ReflectAdapterOnChangeDueJob: Unify.Framework.UnifyEngineException: The connector job ChangeDetectionSchedulerJobDecorator could not be run as the Chris21 Person Connector is currently disabled at Unify.Product.IdentityBroker.ChangeDetectionEnablementJobDecorator.<>c__DisplayClass2.<.ctor>b__0() at Unify.Framework.BeforeJobDecorator.Run() at Unify.Product.IdentityBroker.QueuedConnectorExecutionProcessorEndDecorator.Run()",Normal
Although it is describing the correct behaviour (an attempt to run a job was made, which required a disabled connector) the way in which it logged it was not useful, and would be worrying for implementers encountering this.
Firstly, this is not an Error, it is either a Warning or possibly information data. Secondly, considering it happens under the covers the logging level might need to be reassessed, as this will fill the logs quickly if the job is left unattended.
Customer support service by UserEcho
Assigned to Tony after discussion.
Reassigned for confirmation of completion.