WCC is not able to connect EEM Server with updated dns name

book

Article ID: 241615

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

We have changed the DNS name and the IP of the EEM Server( old name was <old machine name> and the new name is <new machine name>). The Scheduler is working fine with this EEM server(with new DNS name) after the change in autosys_secure but WCC is not working despite of update in the file  :

We have checked with restaring 1) S99igateway and 2) WCC Services. Please help.

In reviewing the CA-wcc.log on the Primary Scheduler machine, seeing the below error messages:

INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 | Caused by: java.io.IOException: No available connection to address [<secondary wcc machine>]:7004
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.client.spi.impl.SmartClientInvocationService.getOrTriggerConnect(SmartClientInvocationService.java:72)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.client.spi.impl.SmartClientInvocationService.invokeOnPartitionOwner(SmartClientInvocationService.java:45)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.client.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:150)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.client.spi.impl.ClientInvocation.retry(ClientInvocation.java:178)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.client.spi.impl.ClientInvocation.run(ClientInvocation.java:166)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at com.hazelcast.util.executor.LoggingScheduledExecutor$LoggingDelegatingFuture.run(LoggingScheduledExecutor.java:160)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
INFO   | jvm 1    | 2022/05/06 13:42:57 |      935 |  at java.lang.Thread.run(Thread.java:821)

 

Environment

Release : 11.4.7

Component : WORKLOAD CONTROL CENTER

Resolution

The /etc/hosts file had the wrong hostname for the Primary WCC hostname. Corrected the hostname and bounced the WCC processes.