WCC does not seem to be collecting data from Autosys or updated/correct statuses are not reflecting properly in WCC
search cancel

WCC does not seem to be collecting data from Autosys or updated/correct statuses are not reflecting properly in WCC

book

Article ID: 272037

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

WCC does not seem to be collecting data from Autosys after a restart of WCC.   

Collector logs only contain lines like this, but no real job collection going on.  Bolded message seems to repeat again and again

INFO   | jvm 1    | 2023/08/19 12:28:22 |     7319 | @collector 7004_PRD_SCHEDULER_JOB                                       []  INFO #CollectorHelper                    # CollectorHelper::getAEServer: Server not found for servername PRD_SCHEDULER, loading fresh...
INFO   | jvm 1    | 2023/08/19 12:28:22 |     7319 | @collector 7004_PRD_SCHEDULER_JOB                                       []  INFO #CollectorJobExecutionListener      # JOB collecting started for server: PRD_SCHEDULER
INFO   | jvm 1    | 2023/08/19 12:28:23 |     7320 | @collector 7004_PRD_SCHEDULER_JOB                                       []  INFO #JobsJpaWriter                      # 26 job(s) to be added/updated on server :PRD_SCHEDULER

Environment

Release : 11.3.6

Resolution

- Stop WCC on all WCC nodes

- Start WCC only one node,  make sure collector shows good job collection going on

-  Verify Quickview to see if jobs are responding quickly

- Then start other WCC nodes. the collection tasks get distributed automatically by underlying Hazelcast clustering module that WCC uses.  There is no control on that.