WCC Job Status Synchronization and Timeout Issues Between Nodes (Autosys Workload Automation)

Products

• Autosys Workload Automation

Issue/Introduction

When running WCC in a high-availability (HA) cluster, job statuses may appear out of sync or timeout in the Monitoring view.
This article provides troubleshooting steps to resolve communication issues between WCC nodes.

Environment

• Autosys Workload Automation (all versions)
• WCC HA Cluster / Multi-node deployments

Cause

WCC nodes in a cluster share cache for job status monitoring.
This communication relies on the Hazelcast protocol, which uses TCP port 7004 by default. If this port is blocked in either the inbound or outbound traffic rules between WCC nodes, the nodes cannot synchronize data, leading to timeouts and "stale" job statuses.

Resolution

1. Verify Firewall Configuration: Ensure that TCP port 7004 is open for traffic in both directions (inbound and outbound) between all WCC nodes in the HA cluster.
2. Test Connectivity: Use telnet or nc commands between the nodes to confirm port 7004 is reachable.
   • Example: telnet <Target_WCC_Node_IP> 7004
3. Check Service Status: If port 7004 is open, verify the WCC services on each node are running and that no other application is binding to port 7004.
4. Review Logs: Inspect the WCC Collector logs (WCC_COLLECTOR.LOG) for communication exceptions or connection-refused errors.
   
   Note: If the issue persists after verifying port 7004, please gather WCC logs and contact Broadcom Support.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.