Resolve does not finish

English Forum Software-Development
1

Hello all,

after updating my OpenEMS I was not able to finish the resolving process anymore. It did not throw any error, it just got stuck for 30 minutes at (see image):

Resolving requirement osgi.extender;filter:='((osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))'

I tried to narrow down the problem by removing bundles from the run requirements and it turned out that resolving worked again smoothly after removing the bundle “io.openems.edge.controller.api.rest” from the list.

resolving_problem
resolving_problem1304×911 64.5 KB

I am using Eclipse 2024-09, the latest OpenEMS-version, Java17 (Eclipse Adoptium\jdk-17.0.10.7-hotspot) and could reproduce the problem both on Win10 and Win11.

Can anyone else reproduce the problem?
Is there a fix to it since I need the REST-API?

Thanks in advance!

Regards
Alex

2

Just restart the IDE and try again :slight_smile:

3

It was worth a try but unfortunately it did not help…

Also I had the problem on to different computers.

4

I found the solution:

org.apache.felix.http.servlet-api

is missing in the “Run Requirements”

5

Thank you so much for finding this! The issue was existing since the latest update of bndtools:

I added your fix there and it’s now building and resolving properly. :+1:

Regards,
Stefan

6

Hi @stefan.feilmeier ,

since this commit my CI Build fails:

The Daemon will expire after the build after running out of JVM heap space.
The project memory settings are likely not configured or are configured to an insufficient value.
The daemon will restart for the next build, which may increase subsequent build times.
These settings can be adjusted by setting 'org.gradle.jvmargs' in 'gradle.properties'.
The currently configured max heap space is '512 MiB' and the configured max metaspace is '256 MiB'.
For more information on how to set these values, please refer to https://docs.gradle.org/8.11.1/userguide/build_environment.html#sec:configuring_jvm_memory in the Gradle documentation.
To disable this warning, set 'org.gradle.daemon.performance.disable-logging=true'.
Daemon will be stopped at the end of the build after running out of JVM heap space
The Daemon will expire immediately since the JVM garbage collector is thrashing.
The project memory settings are likely not configured or are configured to an insufficient value.
The memory settings for this project must be adjusted to avoid this failure.
These settings can be adjusted by setting 'org.gradle.jvmargs' in 'gradle.properties'.
The currently configured max heap space is '512 MiB' and the configured max metaspace is '256 MiB'.
For more information on how to set these values, please refer to https://docs.gradle.org/8.11.1/userguide/build_environment.html#sec:configuring_jvm_memory in the Gradle documentation.
To disable this warning, set 'org.gradle.daemon.performance.disable-logging=true'.
Daemon is stopping immediately since the JVM garbage collector is thrashing

FAILURE: Build failed with an exception.

* What went wrong:
Gradle build daemon has been stopped: since the JVM garbage collector is thrashing

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

How could I resolve this Issue?

Greetings!

7

Fixed with:

org.gradle.jvmargs=-Xms1g -Xmx2g “-XX:MaxMetaspaceSize=256m”

Thanks either way ! :slight_smile: