JobScheduler Active Cluster produces large logs files

Current behavior

• If JobScheduler is being configured in a Active Cluster setup, the JobScheduler repeatedly calculate next run time for the distributed orders.
• To keep status of distributed orders in sync, JobScheduler instance calculate order's run time and communicate with other Cluster members via database.
• JobScheduler writes a debug log message with log category scheduler.order

  21 07:00:22.029     0 32285.5A646700 {scheduler.order} Order_queue sos/job_chain_delete_core_files:100  sos::scheduler::order::Order_queue::set_next_announced_distributed_order_time(never), previously 2015-12-21 07:10:00.000+0100
  21 07:00:22.029     0 32285.5A646700 {scheduler.order} Order_queue sos/job_chain_sos_oradb_files:100  sos::scheduler::order::Order_queue::set_next_announced_distributed_order_time(never), previously 2016-01-05 18:00:00.000+0100
  21 07:00:22.029     0 32285.5A646700 {scheduler.order} Order_queue sos/job_chain_run_check_sos_ref:100  sos::scheduler::order::Order_queue::set_next_announced_distributed_order_time(never), previously 2016-01-14 12:40:00.000+0100
  

• The log category scheduler.order is by default active, this results in large number of log messages which in turn make the scheduler.log file very large.

Desired behavior

• The log category scheduler.order should not be enabled by default.