JCP processes fall

[Santiago Fernandez]

Within a v12.3 to v24 update project,
we have the following error when booting the system, since the JCP processes come down.
(see attached screenshot and logs)
Thank you very much in advance
Regards

------------------------------
Santiago Fernández
UC SOFTWARE
[e-mail]
------------------------------

Attachment(s)

CPsrv_trc_007_00.txt   98 KB 1 version

CPsrv_log_007_00.txt   65 KB 1 version

CPsrv_trc_007_01.txt   101 KB 1 version

[Peter Grundler]

Hi Santiago,

the log and traces provided are from a REST API process, not a JCP.

Nevertheless, the log shows an error when binding the port number 8088

regards,
Peter

------------------------------
Automic Certified Professional/Expert & Broadcom Knight

For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
------------------------------

[Peter Grundler]

Hi Santiago,

the log of the REST API process shows a bind error:

Exception 'java.io.IOException: "Failed to bind to 0.0.0.0/0.0.0.0:8088"' at 'org.eclipse.jetty.server.ServerConnector.openAcceptChannel():344'.
The previous error was caused by 'java.net.BindException: "Address already in use: bind"' at 'sun.nio.ch.Net.bind0()'.

It seems that port 8088 is already in use by another program. You now have 2 options:

1. kill the running process that currently uses 8088 and afterwards start the new Rest API process
2. configure a different port number (i.e. 8089)

BTW: the ServiceManager Dialog is not showing a Rest API line ...

regards,
Peter

------------------------------
Automic Certified Professional/Expert & Broadcom Knight

For AUTOMIC trainings please check https://www.qskills.de/qs/workshops/automic/
------------------------------

[Michael Dolinek]

Hi @Santiago Fernandez

be aware that v24.x (and already v21) has 5 different process types. They are named CP, WP, JCP, JWP and REST. You need at minimum 1 of each.

see https://docs.automic.com/documentation/webhelp/english/AA/24.2/DOCU/24.2/Automic%20Automation%20Guides/Content/_Common/Welcome/AWA/AWAArchitecture.htm?tocpath=Welcome%7C_____3

This page gives an overview on how to setup/configure these process types: 

https://docs.automic.com/documentation/webhelp/english/AA/24.2/DOCU/24.2/Automic%20Automation%20Guides/Content/Installation_Manual/AE/InstalltheAE_ServerManager_JWP_JCP.htm?tocpath=Installing%7CManual%20Installation%7CInstalling%20the%20Automation%20Engine%20(AE)%7CInstalling%20the%20AE%252C%20ServiceManager%252C%20JWP%252C%20REST%20and%20JCP%7C_____0

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Michael A. Lowry]

Some big networking changes were introduced with v21, so if you're upgrading from v12.3 you should definitely familiarize yourself with these changes. This diagram might help. It's applicable to v24.2 as well.

AWI v21 inter-process communication

[Markus Embacher]

Hi Santiago, 

it looks like you are trying to start multiple REST processes using the same port. One REST process per Node is normally sufficient. Start multiple JCPs instead. Is there a specific reason you are still keeping CP processes?

Regards, Markus

[Santiago Fernandez]

Thank you all for your collaboration. We already have all the different types of processes in green.
It was a certificate problem, by deleting a REST that was launched and adjusting the certificate again, it was solved. As Markus pointed out, only one was necessary.
Thank you all very much

------------------------------
Santiago Fernández
UC SOFTWARE
[e-mail]
------------------------------