The TLS Gateway does not stop when one of the ports cannot be bound upon startup

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The TLS Gateway does not stop when one of the ports cp_port or gss_port set in the ini file cannot be bound upon startup as it does with the tls_port showing this error message:

U02100037 Unable to start the TLS-Gateway, reason java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:2300.

Expected behavior: TLS Gateway should trigger an immediate shutdown upon startup in case it fails to bind to one of the ports cp_port, gss_port or tls_port
Actual behavior: TLS Gateway starts normally and does not throw any error if the cp_port or gss_port set in the ini file cannot be bound upon startup.

Environment

Automation Engine 21.0.x and 24.x

Cause

Defect

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine
Will be fixed in Automation.Engine 21.0.10 - Planned release end April 2024
Will be fixed in Automation.Engine 24.1.0 - Planned release end June 2024

Additional Information

Defect ID: AE-35282

Public Description: A problem has been fixed where the TLS Gateway starts normally and does not throw any error if the cp_port or gss_port set in the ini file cannot be bound upon startup.