Multiple WPs show running on PWP port in Administration perspective
search cancel

Multiple WPs show running on PWP port in Administration perspective

book

Article ID: 394254

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When a system has hostname= set in the ucsrv.ini file and a WP is started followed by at least one JWP, followed by at least one more WP, Processes and Utilization will show two WPs as having the PWP port.

For instance:

  1. Have a system running
  2. Stop all WPs
  3. In ucsrv.ini, set a hostname= with a fully qualified domain name (fqdn) like automic.exampe.com
  4. Start only one WP and it will then become a PWP
  5. Start one JWP and wait until it's shown in the Administration perspective -> Automation Engine Management -> Processes and Utilization
  6. Start two or three more WPs

Now go back to the AE Processes and Utilization and there will now be a second WP that shows the same port as the PWP

Cause

This is caused by a defect that has no functional impact to the system processes

Resolution

This was confirmed as a defect that has no functional impact to the system processes.  Although the non-PWP shows as binding to the same port as the primary worker process, it is not truly bound to that process.  This is planned to be fixed with the Automation Engine component for 21.0.14 and 24.4.1.