Starting Platform failed (Vagrant installation method)

Hi,
I'm far away from beeing familiar with Java ecosystem so sorry for not fully-fledged explanation.

I'm trying to setup GXF Platform using [Vagrant Installation Guide](https://grid-exchange-fabric.gitbook.io/gxf/userguide/installationguide/installation/setup-vm-vagrant) and [Platform Setup](https://grid-exchange-fabric.gitbook.io/gxf/userguide/installationguide/setuposgp), unfortunatelly without success 😢.
After completing all previous steps i stumble at [Starting Apache Tomcat Server](https://grid-exchange-fabric.gitbook.io/gxf/userguide/installationguide/setuposgp#starting-apache-tomcat-server) or even ealier.

Java & Maven version:
```shell
dev@dev-box:/home/dev$ mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /home/dev/Tools/apache-maven-3.8.6
Java version: 17.0.5, vendor: Eclipse Adoptium, runtime: /home/dev/.sdkman/candidates/java/17.0.5-tem
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-204-generic", arch: "amd64", family: "unix"

ev@dev-box:/home/dev$ java -version
openjdk version "17.0.5" 2022-10-18
OpenJDK Runtime Environment Temurin-17.0.5+8 (build 17.0.5+8)
OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (build 17.0.5+8, mixed mode, sharing)

```


* The first problem is that vagrant [OSGP/Config/puppet/manifests/install-dev-env.pp](https://github.com/OSGP/Config/blob/cf032d40025dddd4c86e9d3b795a0e8ad6c89685/puppet/manifests/install-dev-env.pp#L24) is trying to download maven from wrong url , this one [link](https://github.com/PiotrBzdrega/Config/blob/77a69baad5019a847bfe736293f4f4b85ea3d945/puppet/manifests/install-dev-env.pp#L24C51-L24C161) is correct. After that and some picture [wrong url fix](https://github.com/OSGP/Config/commit/c4e107654210e93ac43bba7b479d3e19e159fbbf).
[Vagrant up](https://github.com/user-attachments/files/18505804/vagrant_up.txt) is done without errors.


* The second ... Imported Projects contains bunch of errors
```java
/home/dev/Sources/OSGP/open-smart-grid-platform/osgp/protocol-adapter-iec60870/osgp-protocol-simulator-iec60870/target/m2e-wtp/web-resources/META-INF/MANIFEST.MF (No such file or directory)	pom.xml	/osgp-protocol-simulator-iec60870	line 1	Maven Configuration Problem
/home/dev/Sources/OSGP/open-smart-grid-platform/osgp/protocol-adapter-iec61850/osgp-protocol-simulator-iec61850/target/m2e-wtp/web-resources/META-INF/MANIFEST.MF (No such file or directory)	pom.xml	/osgp-protocol-simulator-iec61850	line 1	Maven Configuration Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	device-status.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	device.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	error.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	home.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	list.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
Can not find the tag library descriptor for "http://java.sun.com/jsp/jstl/core"	switch-result.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 656	WSDL Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 658	WSDL Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 660	WSDL Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 672	WSDL Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 674	WSDL Problem
The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	SmartMeteringMonitoring.wsdl	/osgp-ws-smartmetering/src/main/resources	line 676	WSDL Problem
The input element is referencing an undefined message 'DecoupleMbusDeviceAdministrativeAsyncRequest'. Check that the message name and namespace are correct and that the message has been defined.	SmartMeteringInstallation.wsdl	/osgp-ws-smartmetering/src/main/resources	line 199	WSDL Problem
The output element is referencing an undefined message 'DecoupleMbusDeviceAdministrativeAsyncResponse'. Check that the message name and namespace are correct and that the message has been defined.	SmartMeteringInstallation.wsdl	/osgp-ws-smartmetering/src/main/resources	line 194	WSDL Problem
The output element is referencing an undefined message 'DecoupleMbusDeviceAdministrativeResponse'. Check that the message name and namespace are correct and that the message has been defined.	SmartMeteringInstallation.wsdl	/osgp-ws-smartmetering/src/main/resources	line 202	WSDL Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	add-device.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	add-result.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	create.jsp	/web-device-simulator/src/main/webapp/WEB-INF/views/devices	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	device-status.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	device.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	edit.jsp	/web-device-simulator/src/main/webapp/WEB-INF/views/devices	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	error.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	home.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	list.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	list.jsp	/web-device-simulator/src/main/webapp/WEB-INF/views/devices	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	list.jsp	/web-device-simulator/src/main/webapp/WEB-INF/views/logs	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	nav.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path	switch-result.jsp	/web-demo-app/src/main/webapp/WEB-INF/views	line 1	JSP Problem
```
 I was trying to make mvn clean install in `/home/dev/Sources/OSGP/open-smart-grid-platform`, but it did not allows me to build all projects: 
[mvn_clean_install.log](https://github.com/user-attachments/files/18507586/mvn_clean_install.log)

```java
[ERROR] Tests run: 1872, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for open-smart-grid-platform 6.13.0-SNAPSHOT:
[INFO] 
[INFO] super-osgp ......................................... SUCCESS [  0.386 s]
[INFO] parent-platform .................................... SUCCESS [  0.009 s]
[INFO] parent-shared ...................................... SUCCESS [  0.016 s]
[INFO] shared ............................................. SUCCESS [ 16.631 s]
[INFO] osgp-throttling-api ................................ SUCCESS [  2.152 s]
[INFO] osgp-throttling-service ............................ SUCCESS [ 16.856 s]
[INFO] osgp-domain-core ................................... SUCCESS [ 12.733 s]
[INFO] osgp-domain-logging ................................ SUCCESS [  2.986 s]
[INFO] osgp-adapter-domain-shared ......................... SUCCESS [  2.648 s]
[INFO] osgp-dto ........................................... SUCCESS [  7.740 s]
[INFO] osgp-adapter-domain-admin .......................... SUCCESS [  5.511 s]
[INFO] osgp-adapter-domain-core ........................... SUCCESS [ 15.650 s]
[INFO] osgp-ws-core ....................................... SUCCESS [  5.740 s]
[INFO] osgp-adapter-ws-shared ............................. SUCCESS [ 12.675 s]
[INFO] osgp-adapter-ws-shared-db .......................... SUCCESS [  3.998 s]
[INFO] osgp-adapter-ws-core ............................... SUCCESS [ 18.448 s]
[INFO] osgp-ws-admin ...................................... SUCCESS [  2.472 s]
[INFO] osgp-adapter-ws-admin .............................. SUCCESS [  5.594 s]
[INFO] osgp-logging ....................................... SUCCESS [  4.621 s]
[INFO] osgp-core .......................................... SUCCESS [ 16.132 s]
[INFO] osgp-adapter-domain-publiclighting ................. SUCCESS [ 10.875 s]
[INFO] osgp-adapter-domain-tariffswitching ................ SUCCESS [  6.440 s]
[INFO] osgp-ws-publiclighting ............................. SUCCESS [  3.060 s]
[INFO] osgp-adapter-ws-publiclighting ..................... SUCCESS [  9.773 s]
[INFO] osgp-ws-tariffswitching ............................ SUCCESS [  2.542 s]
[INFO] osgp-adapter-ws-tariffswitching .................... SUCCESS [  6.049 s]
[INFO] osgp-adapter-domain-smartmetering .................. SUCCESS [ 36.423 s]
[INFO] osgp-ws-smartmetering .............................. SUCCESS [  4.844 s]
[INFO] osgp-adapter-ws-smartmetering ...................... SUCCESS [ 25.632 s]
[INFO] osgp-ws-secret-management .......................... SUCCESS [  2.317 s]
[INFO] osgp-secret-management ............................. SUCCESS [ 14.741 s]
[INFO] platform ........................................... SUCCESS [  0.047 s]
[INFO] osgp-throttling-client ............................. SUCCESS [  9.209 s]
[INFO] osgp-jasper-shared ................................. SUCCESS [  3.674 s]
[INFO] osgp-kafka-config .................................. SUCCESS [  6.974 s]
[INFO] shared ............................................. SUCCESS [  0.013 s]
[INFO] parent-pa-oslp ..................................... SUCCESS [  0.008 s]
[INFO] oslp ............................................... SUCCESS [ 21.614 s]
[INFO] osgp-web-device-simulator .......................... SUCCESS [ 10.946 s]
[INFO] osgp-core-db-api ................................... SUCCESS [  2.706 s]
[INFO] osgp-protocol-adapter-oslp-elster .................. SUCCESS [ 15.268 s]
[INFO] signing-server ..................................... SUCCESS [  5.357 s]
[INFO] protocol-adapter-oslp .............................. SUCCESS [  0.011 s]
[INFO] parent-pa-iec60870 ................................. SUCCESS [  0.008 s]
[INFO] osgp-iec60870 ...................................... SUCCESS [  7.274 s]
[INFO] osgp-protocol-adapter-iec60870 ..................... SUCCESS [ 14.300 s]
[INFO] osgp-protocol-simulator-iec60870 ................... SUCCESS [ 19.933 s]
[INFO] protocol-adapter-iec60870 .......................... SUCCESS [  0.004 s]
[INFO] parent-pa-iec61850 ................................. SUCCESS [  0.005 s]
[INFO] osgp-iec61850 ...................................... SUCCESS [  4.731 s]
[INFO] osgp-core-db-api-iec61850 .......................... SUCCESS [  4.288 s]
[INFO] osgp-protocol-adapter-iec61850 ..................... SUCCESS [ 13.957 s]
[INFO] osgp-protocol-simulator-iec61850 ................... SUCCESS [  5.235 s]
[INFO] protocol-adapter-iec61850 .......................... SUCCESS [  0.060 s]
[INFO] parent-pa-dlms ..................................... SUCCESS [  0.072 s]
[INFO] osgp-dlms .......................................... SUCCESS [ 12.961 s]
[INFO] jasper-interface ................................... SUCCESS [ 27.739 s]
[INFO] osgp-protocol-adapter-dlms ......................... FAILURE [03:03 min]
[INFO] osgp-protocol-simulator-dlms ....................... SKIPPED
[INFO] dlms-device-simulator .............................. SKIPPED
[INFO] osgp-simulator-dlms-triggered ...................... SKIPPED
[INFO] dlms-device-simulator-starter ...................... SKIPPED
[INFO] simulator .......................................... SKIPPED
[INFO] protocol-adapter-dlms .............................. SKIPPED
[INFO] osgp ............................................... SKIPPED
[INFO] parent-integration-tests ........................... SKIPPED
[INFO] cucumber-tests-core ................................ SKIPPED
[INFO] cucumber-tests-execution ........................... SKIPPED
[INFO] cucumber-tests-platform ............................ SKIPPED
[INFO] cucumber-tests-platform-common ..................... SKIPPED
[INFO] cucumber-tests-protocol-iec60870 ................... SKIPPED
[INFO] cucumber-tests-platform-publiclighting ............. SKIPPED
[INFO] cucumber-tests-platform-smartmetering .............. SKIPPED
[INFO] integration-tests .................................. SKIPPED
[INFO] parent-os-webapps .................................. SKIPPED
[INFO] osgp-web-demo-app .................................. SKIPPED
[INFO] public-lighting-demo-app ........................... SKIPPED
[INFO] open-smart-grid-platform ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10:46 min
[INFO] Finished at: 2025-01-22T14:42:18Z
[INFO] ------------------------------------------------------------------------
```
I was able to "solve" or maybe only hide 🤔 2 problems

- [x] The superclass "javax.servlet.http.HttpServlet", determined from the Dynamic Web Module facet version (2.5), was not found on the Java Build Path
I just changed `Dynamic Web Module 2.5 >> 5.0` for not valid projects 

![Image](https://github.com/user-attachments/assets/565b6fd1-bc73-4336-b900-ab3e6e9a1535)


- [x] The 'ActionHeader' message specified for the SOAP header is undefined. The message specified must be defined in the WSDL document.	

I added to SmartMeteringMonitoring.wsdl:
```java
  <wsdl:message name="ActionHeader">
    <wsdl:part element="common:OrganisationIdentification"
      name="OrganisationIdentification" />
    <wsdl:part element="common:UserName" name="UserName" />
    <wsdl:part element="common:ApplicationName" name="ApplicationName" />
  </wsdl:message>
```
## Update

I made again 'mvn clean install' and everything was successfully build.
In Eclipse still persist some faults, but i started server

Unfortunately after some time, info about not correctly started server showed up.
Here is the full log from tomcat starting

[tomcat_full.log](https://github.com/user-attachments/files/18515878/tomcat_full.log)


After i got info from eclipse that starting server failed activemq started to throws warnings:
```shell
 INFO | No Spring WebApplicationInitializer types detected on classpath
 INFO | ActiveMQ WebConsole available at http://0.0.0.0:8161/
 INFO | ActiveMQ Jolokia REST API available at http://0.0.0.0:8161/api/jolokia/
 INFO | Initializing Spring FrameworkServlet 'dispatcher'
 INFO | No Spring WebApplicationInitializer types detected on classpath
 INFO | jolokia-agent: Using policy access restrictor classpath:/jolokia-access.xml
 WARN | Transport Connection to: tcp://127.0.0.1:40658 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40686 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40608 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45822 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40734 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45812 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40714 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40764 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40698 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40636 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45800 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:40772 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45660 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45688 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45630 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45626 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45740 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45612 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45724 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45758 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45708 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45646 failed: java.io.EOFException
 WARN | Transport Connection to: tcp://127.0.0.1:45604 failed: java.io.EOFException
(...)
```




Let me know if there is something that i should verify/modify

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Starting Platform failed (Vagrant installation method) #294

Update

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Starting Platform failed (Vagrant installation method) #294

Description

Update

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions