Connection to the AE system not possible. No connection to the following CPs could be established: hostname:8420

[Maria Joseph Vimalan]

Dear Experts,

We are trying to upgrade the AE 21 version in our SBX which is running on AE 12.3 AE DB, Utlities,  AE binaries, Service manager, Service Manager dialog are upgraded successfully.

During the update of AWI on Tomcat, we are unable to connect AWI with AE.

We could see the WS port is created successfully

20220223/180816.186 - 34 Jetty: Logging initialized @7260ms to com.automic.agents.impl.AgentLogBridge
20220223/180816.289 - 34 Jetty: jetty-9.4.40.v20210413; built: 2021-04-13T20:42:42.668Z; git: b881a572662e1943a14ae12e7e1207989f218b74; jvm 1.8.0_321-b07
20220223/180816.321 - 34 Jetty: DefaultSessionIdManager workerName=node0
20220223/180816.321 - 34 Jetty: No SessionScavenger set, using defaults
20220223/180816.321 - 34 Jetty: node0 Scavenging every 600000ms
20220223/180816.399 - 34 Jetty: Started o.e.j.s.ServletContextHandler@2f915e8{/,null,AVAILABLE}
20220223/180816.482 - 34 Jetty: x509=X509@62ebf23(hostname,h=[],w=[]) for Server@1735783f[provider=null,keyStore=file:///D:/Automic_Engine/AutomationEngine/bin/automic-sbx,trustStore=null]
20220223/180816.513 - 34 Jetty: Started ServerConnector@1a9904bf{SSL, (ssl, http/1.1)}{0.0.0.0:8420}
20220223/180816.513 - 34 Jetty: Started @7599ms

we created a der certificate file using keystore explorer from keyfile used for AE.   We put the location of the der file in the uc4config.xml file. 
However when we try to connect to AWI , we get the below error


in AWI logs, we get the below error
 
2022-02-23 21:49:06,364 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Starting: Opening connection to hostname/Ip address:8420
2022-02-23 21:49:06,364 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Loading certificates from directory: 'D:\certs'.
2022-02-23 21:49:06,380 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Certificate loaded from file 'D:\certs\automic-sbx.der'.
2022-02-23 21:49:06,380 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - adding 90 certificates from the default trust manager
2022-02-23 21:49:06,442 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient started.
2022-02-23 21:49:06,552 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient has no more active sessions and will shut down.
2022-02-23 21:49:06,567 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient stopped.
2022-02-23 21:49:10,405 pool-1-thread-2 [WARN ] NOLOGIN/- 8E84C96FD617944ABB73EC68D76B78B5-0 [com.uc4.ecc.framework.core.inject.AEAwareScope] - Cannot inject Key[type=com.uc4.ecc.framework.core.interfaces.IContentService, annotation=[none]] when no AE Connection is set on context.
2022-02-23 21:49:19,393 ps-jsse-nio-443-exec-2 [WARN ] NOLOGIN/- 8E84C96FD617944ABB73EC68D76B78B5-0 [com.uc4.ecc.framework.core.inject.AEAwareScope] - Cannot inject Key[type=com.uc4.ecc.framework.core.interfaces.ISessionShutdownService, annotation=[none]] when no AE Connection is set on context.
2022-02-23 21:49:19,393 ps-jsse-nio-443-exec-2 [WARN ] NOLOGIN/- 8E84C96FD617944ABB73EC68D76B78B5-0 [com.uc4.ecc.framework.core.inject.AEAwareScope] - Cannot inject Key[type=com.uc4.ecc.framework.core.interfaces.IContentService, annotation=[none]] when no AE Connection is set on context.

content of uc4config.xml file

<?xml version="1.0" encoding="ISO-8859-15"?>
<configuration>
<!-- 0: off, 1: send, 2: receive, >=3: all -->
<trace count="10" xml="2"></trace>
<connections trustedCertFolder="D:\certs\">
<connection name="AutomicSandbox" system="SBX">
<cp ip="<hostname>" port="8420"/>
</connection>
</connections>
</configuration>


Any suggestions from your side please. 

Thanks and Regards
Vimalan

[Support Technique Highway]

Hello Maria,

"2022-02-23 21:49:06,442 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient started.
2022-02-23 21:49:06,552 Thread-16 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient has no more active sessions and will shut down."
==> seems to be an issue with your configuration.

The default port for WS (JCP) is 8443. Have you correctly defined it into INI file of your AE?
Could you check with "netstat" command if you see it as a LISTEN port?

What about the logs at Automation Engine level? do you see your connection attempt?

Best regards
TC

[Maria Joseph Vimalan]

Hi TC,

Yes the default port is 8443 but as mentioned from the JCP logs, we see it is getting connected to 8420
20220223/180816.513 - 34 Jetty: Started ServerConnector@1a9904bf{SSL, (ssl, http/1.1)}{0.0.0.0:8420}

However I tried to change the WS Port to 8443 but still doesn't work. I don't see any hit on the JCP logs when the connection attempt's are made.

Any other clue please ? 

Regards,
Vimalan

[Support Technique Highway]

Hi Vimalan,

If you don't have any logs from AE perspective, it means the communication is not even initialized.
In your AE INI file, you should have this kind of entries to define the port number of your server processes:

[PORTS]
CP.PORTS=2217-2226
WS.PORT=8443
JWP.SYNC.PORTS=3271-3279
JCP.PORTS=2317

WS port number is one of them, and you should retrieve it when you start your AE.
As requested previously, could you please try to execute this command: netstat -lpn | grep 8443
You should get a response so that you can confirm there is effectively a listening port number pointing to 8443 on your AE.

Other point, in case you are using a remote Web application server (Tomcat or whatever), is the flow open?
Please check this with the following command: telnet <AE_hostname> <WS_port>

If both tests are OK, I propose you to fully stop your AE, and restart the server processes by following this startup sequence: WP ⇒ JWP ⇒ REST ⇒ CP ⇒ JCP
Please take some time between each type of server processes, and check in the corresponding log if something went wrong. Normally, you get this kind of entries:
"U00003486 ListenSocket with port number '2317' successfully created."
"U00003471 The Server '***#CP001' has successfully been initialized, *** R E A D Y F O R R U N ***"

Best regards,
TC

[Maria Joseph Vimalan]

Hi , 

Thank you for your feedback. I have tried exactly the steps you have requested but still of no luck.

2022-02-25 22:19:36,645 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Starting: Opening connection to <hostname>/<IP Address>:8433
2022-02-25 22:19:36,645 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Loading certificates from directory: 'D:\certs'.
2022-02-25 22:19:36,660 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - Certificate loaded from file 'D:\certs\automic-sbx.der'.
2022-02-25 22:19:36,660 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - adding 90 certificates from the default trust manager
2022-02-25 22:19:36,723 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient started.
2022-02-25 22:19:38,823 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient has no more active sessions and will shut down.
2022-02-25 22:19:38,823 Thread-14 [TRACE] NOLOGIN/- NOUI [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient stopped.

i started the work processes as you have suggested with a gap of 5 seconds . 



I'm attaching the JCP logs here. 

Any idea here please? 

Regards
Vimalan

Attachment(s)

CPsrv_log_013_00.txt   57 KB 1 version

[Maria Joseph Vimalan]

Attaching AWI logs also

Attachment(s)

ABCDEFG1012_awi_LOG.00.txt   496 KB 1 version

[Maria Joseph Vimalan]

Dear all

The issue is fixed. The key alias was in upper case but in the certificate we had in lower case.

Thank you Peter for finding it so quickly.

Thanks and Regards
Vimalan