JCP takes last CP/Port number defined in UCSrv.ini file.
Article ID: 84755
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
The behavior introduced with the Java Communication Process (JCP) to select the port and/or Communication Process (CP) numbers does not follow the previous practice of selecting the next available CP/port from the ini file.
Expected Behavior:
The automation engine selects the next available CP port number from the list of port numbers in the UCSrv.ini file to assign to the JCP.
Actual Behavior:
The automation engine is selecting the highest available CP port number from the list of port numbers in the UCSrv.ini file to assign to the JCP.
N/A
The behavior introduced with the Java Communication Process (JCP) to select the port and/or Communication Process (CP) numbers does not follow the previous practice of selecting the next available CP/port from the ini file.
Expected Behavior:
The automation engine selects the next available CP port number from the list of port numbers in the UCSrv.ini file to assign to the JCP.
Actual Behavior:
The automation engine is selecting the highest available CP port number from the list of port numbers in the UCSrv.ini file to assign to the JCP.
Cause
Cause type:
By design
Root Cause: Change was made intentionally, but not documented.
By design
Root Cause: Change was made intentionally, but not documented.
Environment
Release: AUTWAB99000-12.0-Automic Workload Automation-Base Edition
Component:
Component:
Resolution
The following change was made to the documentation:
Fix Status: No Fix
- Work process names start with the letters WP followed by the next available process number.
- Communication process names start with CP followed by the next available process number.
- The name of a JCP also starts with CP but for load-balancing reasons, it uses the highest available process number.
Fix Status: No Fix
Additional Information
Workaround :
N/A
N/A
Feedback
Yes
No
Powered by
