Unable to launch Xflow after upgrade to 17.4.1

Products

• CA Service Management - Service Desk Manager

Issue/Introduction

Unable to launch Xflow after upgrade to 17.4.1 from older version and the following errors are seen in the logs: 

ERROR - 2024-02-13 12:41:43 [akka.io.TcpListener] - Bind failed for TCP channel on endpoint [/0.0.0.0:9444]
java.net.BindException: [/0.0.0.0:9444] Address already in use: bind
 at java.base/sun.nio.ch.Net.bind0(Native Method)
 at java.base/sun.nio.ch.Net.bind(Net.java:459)
 at java.base/sun.nio.ch.Net.bind(Net.java:448)
 at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
 at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80)
INFO - 2024-02-13 12:41:43 [akka.actor.CoordinatedShutdown] - Running CoordinatedShutdown with reason [JvmExitReason]
INFO - 2024-02-13 12:41:44 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] - Marked address [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] as [Leaving]
INFO - 2024-02-13 12:41:44 [a.c.s.ClusterSingletonManager] - Exited [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520].
INFO - 2024-02-13 12:41:44 [a.c.s.ClusterSingletonManager] - Oldest observed OldestChanged: [akka://Incident_MicroService_XflowClusterSystem@m:25520 -> None]
INFO - 2024-02-13 12:41:44 [a.c.s.ClusterSingletonManager] - ClusterSingletonManager state change [Oldest -> WasOldest]
INFO - 2024-02-13 12:41:45 [a.c.s.ClusterSingletonManager] - Singleton manager stopping singleton actor [akka://Incident_MicroService_XflowClusterSystem/user/removeIdleSessionsService/singleton]
INFO - 2024-02-13 12:41:45 [c.c.c.a.s.SessionCleanUpThread] - Stopping SessionCleanUpThread actor...
INFO - 2024-02-13 12:41:45 [a.c.s.ClusterSingletonManager] - ClusterSingletonManager state change [WasOldest -> Stopping]
INFO - 2024-02-13 12:41:45 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] - Leader is moving node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] to [Exiting]
INFO - 2024-02-13 12:41:45 [a.c.s.ClusterSingletonManager] - Singleton actor [akka://Incident_MicroService_XflowClusterSystem/user/removeIdleSessionsService/singleton] was terminated
INFO - 2024-02-13 12:41:45 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] - Exiting completed
INFO - 2024-02-13 12:41:45 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] - Shutting down...
INFO - 2024-02-13 12:41:45 [akka.cluster.Cluster] - Cluster Node [akka://Incident_MicroService_XflowClusterSystem@Server_name:25520] - Successfully shut down
INFO - 2024-02-13 12:41:45 [a.r.RemoteActorRefProvider$RemotingTerminator] - Shutting down remote daemon.
INFO - 2024-02-13 12:41:45 [a.r.RemoteActorRefProvider$RemotingTerminator] - Remote daemon shut down; proceeding with flushing remote transports.
INFO - 2024-02-13 12:41:45 [a.r.RemoteActorRefProvider$RemotingTerminator] - Remoting shut down.

 

Cause

While upgrading to 17.4.1, on the Xflow installation page, if the default port details(non-SSL) are replaced with the SSL port numbers.

Resolution

If you are upgrading to 17.4.1 from an older version and have SSL is in place in the new environment, please make sure that the following are met: 

1) While upgrading the Xflow from an older version to 17.4.1, port numbers(non-SSL) should not be changed and continue with the default ports. 

2) The config.xml from the location Program Files\CA\xFlow\APPS\ServiceConfig.xml  file should have the non-SSL default ports for microservices. 

3) al_cdb_configuration parameters for Xflow microservices must be default non-SSL ports. 

IncidentService Port="9002"
SearchService Port="9006"
PushService Port="9008" 
CollabService Port="9014" 
InsightService Port="9016"