Skip to content

Back-end

Backend does not start

If Service Ui backend does not start. Try to start it at bash / terminal:

Navigate to Service Ui backend folder:

cd service-ui/

Start Service ui backend with installed java version from OS:

java -jar lib/upconnect-core.jar

Start with java runtime delivered with UP at Linux/maxOS:

./jre/bin/java -jar lib/upconnect-core.jar

Start with java runtime delivered with UP at Windows:

jre\bin\java.exe -jar lib\upconnect-core.jar

Since bash does not close if Service Ui backend crashes or does not start, problem should be logged at bash output.

Invalid Java Runtime

Consider that Java runtime (JRE) depends on used operating system.

If Eclipse (UP) runs at different operating system version than deployed Service UI. Copy correct Java runtime (JRE) to /jre folder at Service Ui installation path.
Recommended Java runtime for Service Ui:

https://developer.ibm.com/languages/java/semeru-runtimes/downloads/?os=undefined (Select manually version Java 17 (LTS))

or

https://adoptium.net/de/temurin/releases/?version=17

Java Virtual Machine Exception (Windows)

C:\UP-Workspaces\10021.263.08-Salzbad_Güntensberger_UP-Project\10021.263.08-Salzbad_Güntensberger_UP-Project\UPbuild__ServiceUiBackend\jre>bin\java
JVMJ9VM013W Initialisierungsfehler in Funktion VMInitStages(7): cannot initialize modules path
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Looks like a problem with non ASCII characters at path. Do not use ä, ö, ü, ...

Out of memory Exception

  • Check available memory for Service Ui backend service.

  • Check cached persistence logger data: log/data-logger-storage

  • Delete storage and probably reduce cache size, further informations at: UP - Logger persistence

Web server does not start

If browser does not shows Service Ui Frontend (default: 8080) or Service Ui animation Frontend (default: 8081). Check console log or log/up-connect.log file.

  • 17:49:53.924 [vert.x-worker-thread-1] ERROR (AnimationVerticle.java:52) - Starting animation web server at port 8081 failed: Address already in use

Change web server ports

All ports configured at extended backend configuration (data/config.json):

  • Service Ui webserver: webServer/port: default: 8080
  • Animation webserver: animationWebServer/port: default: 8081

Check binded ports

MacOS / Linux

sbi@NB-MAC-004 ~ % sudo lsof -iTCP -sTCP:LISTEN -n -P
COMMAND     PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
UserEvent   113 root  140u  IPv6 0x3bbf539bfda0a193      0t0  TCP [fe80:4::aede:48ff:fe00:1122]:49153 (LISTEN)
UserEvent   113 root  141u  IPv6 0x3bbf539bfda09b73      0t0  TCP [fe80:4::aede:48ff:fe00:1122]:49154 (LISTEN)
UserEvent   113 root  142u  IPv6 0x3bbf539bfda09553      0t0  TCP [fe80:4::aede:48ff:fe00:1122]:49155 (LISTEN)
UserEvent   113 root  143u  IPv6 0x3bbf539bfda08f33      0t0  TCP [fe80:4::aede:48ff:fe00:1122]:49156 (LISTEN)
UserEvent   113 root  144u  IPv6 0x3bbf539bfda0add3      0t0  TCP [fe80:4::aede:48ff:fe00:1122]:49157 (LISTEN)
eclipse    5095  sbi  143u  IPv6 0x3bbf539c05ea7293      0t0  TCP *:8081 (LISTEN)
idea       6662  sbi   52u  IPv4 0x3bbf539c100036c3      0t0  TCP 127.0.0.1:6942 (LISTEN)
idea       6662  sbi  480u  IPv4 0x3bbf539bfd17e0a3      0t0  TCP 127.0.0.1:63342 (LISTEN)
idea       6662  sbi  617u  IPv4 0x3bbf539c0fe71823      0t0  TCP 127.0.0.1:64120 (LISTEN)
java       6777  sbi  225u  IPv6 0x3bbf539c05ea4dd3      0t0  TCP *:53398 (LISTEN)
java      11702  sbi  226u  IPv6 0x3bbf539c05ea47b3      0t0  TCP *:57085 (LISTEN)

Windows

Use power shell:

power shell Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess

Extended backend configuration

Some special settings like http port (backend web server) or open web browser by default while starting service ui backend is changeable at data/config.json properties at backend target folder. Normal applications should run with default settings.

https property (not working yet)

Secure feature was never tested with actual ProSys OpcUa library. With older version, it was not possible to add generated key:

Generating a keystore file (keystore.jks) at shell: keytool -genkey -v -keystore keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias up-connect

Loading of generated keystore.jks with A-VIS was not successful.