# Resolve does not finish

**URL:** <https://community.openems.io/t/resolve-does-not-finish/3277>\
**Category:** Software-Development\
**Created:** [December 9, 2024, 1:54pm UTC](https://community.openems.io/t/resolve-does-not-finish/3277 "2024-12-09T13:54:52Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex](https://community.openems.io/letter_avatar_proxy/v4/letter/a/db5fbb/32.png) [@Alex](https://community.openems.io/u/Alex)\
**Post date:** [December 9, 2024, 1:54pm UTC](https://community.openems.io/t/resolve-does-not-finish/3277/1 "2024-12-09T13:54:52Z")

</div>

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):

```auto
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](https://community.openems.io/uploads/default/original/2X/2/234988b72ab0f28c2fbfdcd9d7f71c403bab011f.png)

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

---

<div class="post-metadata">

**Author:** ![Sn0w3y](https://community.openems.io/user_avatar/community.openems.io/sn0w3y/32/636_2.png) [@Sn0w3y](https://community.openems.io/u/Sn0w3y)\
**Post date:** [December 9, 2024, 2:58pm UTC](https://community.openems.io/t/resolve-does-not-finish/3277/2 "2024-12-09T14:58:48Z")

</div>

Just restart the IDE and try again 🙂

---

<div class="post-metadata">

**Author:** ![Alex](https://community.openems.io/letter_avatar_proxy/v4/letter/a/db5fbb/32.png) [@Alex](https://community.openems.io/u/Alex)\
**Post date:** [December 9, 2024, 3:34pm UTC](https://community.openems.io/t/resolve-does-not-finish/3277/3 "2024-12-09T15:34:56Z")

</div>

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

Also I had the problem on to different computers.

---

<div class="post-metadata">

**Author:** ![Alex](https://community.openems.io/letter_avatar_proxy/v4/letter/a/db5fbb/32.png) [@Alex](https://community.openems.io/u/Alex)\
**Post date:** [December 10, 2024, 8:02am UTC](https://community.openems.io/t/resolve-does-not-finish/3277/4 "2024-12-10T08:02:11Z")

</div>

I found the solution:

```auto
org.apache.felix.http.servlet-api

```

is missing in the “Run Requirements”

---

<div class="post-metadata">

**Author:** ![stefan.feilmeier](https://community.openems.io/user_avatar/community.openems.io/stefan.feilmeier/32/2585_2.png) [@stefan.feilmeier](https://community.openems.io/u/stefan.feilmeier)\
**Post date:** [December 10, 2024, 10:56pm UTC](https://community.openems.io/t/resolve-does-not-finish/3277/5 "2024-12-10T22:56:03Z")

</div>

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

> <https://github.com/OpenEMS/openems/pull/2899>
>
> Bumps \[biz.aQute.bnd:biz.aQute.bnd.gradle\](https://github.com/bndtools/bnd) from… 7.0.0 to 7.1.0.
> \<details\>
> \<summary\>Release notes\</summary\>
> \<p\>\<em\>Sourced from \<a href="https://github.com/bndtools/bnd/releases"\>biz.aQute.bnd:biz.aQute.bnd.gradle's releases\</a\>.\</em\>\</p\>
> \<blockquote\>
> \<h2\>Bnd/Bndtools 7.1.0\</h2\>
> \<p\>See \<a href="https://github.com/bndtools/bnd/wiki/Changes-in-7.1.0"\>Release Notes\</a\>.\</p\>
> \</blockquote\>
> \</details\>
> \<details\>
> \<summary\>Commits\</summary\>
> \<ul\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/47e504d7881ba466703c55a8dca7b0578561582d"\>\<code\>47e504d\</code\>\</a\> Build Release 7.1.0\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/c3ff1490e5a2d72336e28920711ec0d024c4a801"\>\<code\>c3ff149\</code\>\</a\> build: Build release 7.1.0.RC1\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/2fc3187b1be2e04e78e4056b6c2efae406646b5b"\>\<code\>2fc3187\</code\>\</a\> Merge pull request \<a href="https://redirect.github.com/bndtools/bnd/issues/6363"\>#6363\</a\> from laeubi/process\_with\_conditional\_package\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/cd347e1202077e625bbdd5dadc158adb49e504db"\>\<code\>cd347e1\</code\>\</a\> Merge pull request \<a href="https://redirect.github.com/bndtools/bnd/issues/6365"\>#6365\</a\> from bndtools/dependabot/github\_actions/ruby/setup-r...\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/9aa57efecc7e026646e279307d23ea5edb089e57"\>\<code\>9aa57ef\</code\>\</a\> Bump ruby/setup-ruby from 1.201.0 to 1.202.0\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/ec0fea78a246e66430db06e0e8ad0423ffb59dc2"\>\<code\>ec0fea7\</code\>\</a\> Merge pull request \<a href="https://redirect.github.com/bndtools/bnd/issues/6361"\>#6361\</a\> from bndtools/dependabot/github\_actions/github/codeq...\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/396262634e86aad490df4b43150f3c903c60973f"\>\<code\>3962626\</code\>\</a\> Add testcase for conditional packages with bnd-process\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/fe9a874b3be6e6c2d86625afa55985d1b89c6199"\>\<code\>fe9a874\</code\>\</a\> Bump github/codeql-action from 3.27.0 to 3.27.1\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/e3c95f878d3266b872d5ce3ea81b07e8a99e3f8e"\>\<code\>e3c95f8\</code\>\</a\> Merge pull request \<a href="https://redirect.github.com/bndtools/bnd/issues/6360"\>#6360\</a\> from pkriens/issue/6346-gradle-reference-to-project-...\</li\>
> \<li\>\<a href="https://github.com/bndtools/bnd/commit/aac92718e6b5021548ff6782871a1841f041eee5"\>\<code\>aac9271\</code\>\</a\> Added a method to get the Macro references from a Processor\</li\>
> \<li\>Additional commits viewable in \<a href="https://github.com/bndtools/bnd/compare/7.0.0...7.1.0"\>compare view\</a\>\</li\>
> \</ul\>
> \</details\>
> \<br /\>
> 
> 
> \[!\[Dependabot compatibility score\](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=biz.aQute.bnd:biz.aQute.bnd.gradle&package-manager=maven&previous-version=7.0.0&new-version=7.1.0)\](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
> 
> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting \`@dependabot rebase\`.
> 
> \[//\]: # (dependabot-automerge-start)
> \[//\]: # (dependabot-automerge-end)
> 
> \---
> 
> \<details\>
> \<summary\>Dependabot commands and options\</summary\>
> \<br /\>
> 
> You can trigger Dependabot actions by commenting on this PR:
> \- \`@dependabot rebase\` will rebase this PR
> \- \`@dependabot recreate\` will recreate this PR, overwriting any edits that have been made to it
> \- \`@dependabot merge\` will merge this PR after your CI passes on it
> \- \`@dependabot squash and merge\` will squash and merge this PR after your CI passes on it
> \- \`@dependabot cancel merge\` will cancel a previously requested merge and block automerging
> \- \`@dependabot reopen\` will reopen this PR if it is closed
> \- \`@dependabot close\` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
> \- \`@dependabot show \<dependency name\> ignore conditions\` will show all of the ignore conditions of the specified dependency
> \- \`@dependabot ignore this major version\` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
> \- \`@dependabot ignore this minor version\` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
> \- \`@dependabot ignore this dependency\` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
> 
> 
> \</details\>

I added your fix there and it’s now building and resolving properly. 👍

Regards,  
Stefan

---

<div class="post-metadata">

**Author:** ![Sn0w3y](https://community.openems.io/user_avatar/community.openems.io/sn0w3y/32/636_2.png) [@Sn0w3y](https://community.openems.io/u/Sn0w3y)\
**Post date:** [December 12, 2024, 5:42am UTC](https://community.openems.io/t/resolve-does-not-finish/3277/6 "2024-12-12T05:42:19Z")

</div>

Hi @stefan.feilmeier ,

since this commit my CI Build fails:

```auto
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!

---

<div class="post-metadata">

**Author:** ![Sn0w3y](https://community.openems.io/user_avatar/community.openems.io/sn0w3y/32/636_2.png) [@Sn0w3y](https://community.openems.io/u/Sn0w3y)\
**Post date:** [December 12, 2024, 10:35am UTC](https://community.openems.io/t/resolve-does-not-finish/3277/7 "2024-12-12T10:35:15Z")

</div>

Fixed with:

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

Thanks either way ! 🙂