[Consul]: Service check fails when running apps without Docker

[mraible]

Overview of the issue

I tested my micro frontends demo script with JHipster 8 tonight. I found that when I ran Consul (via Docker Compose), and all the apps with ./gradlew, service checks fail. Everything still works; it's just kinda weird to see indicators that it might not work.

Everything works as expected when running all apps with docker compose up.

Motivation for or Use Case

I don't think this happened with v7.

Reproduce the error

Follow this demo script and you'll see the problem at "Verify everything is started using Consul at http://localhost:8500".

Suggest a Fix

Not sure.

JHipster Version(s)

8.0.0 and spring-boot-3.2 branch.

[mraible]

@deepu105 Any ideas?

[mshima]

The consul container doesn't have access to the service using the published address.
The address should use the domain host.docker.internal so it can be accessible by containers.

My guess is to use:

SERVER_ADDRESS="host.docker.internal" ./gradlew

[mraible]

What I'm trying to say is this is a regression since 7.9.3. If you look at my blog post and search for "You can verify everything is started using Consul", you'll see that all instances are healthy.

When I tried the same steps with v8, it results in the screenshot in this issue's description.

[deepu105]

i need to take a look Thanks & Regards, Deepu

…

On Thu, Nov 30, 2023 at 12:22 AM Matt Raible ***@***.***> wrote: What I'm trying to say is this is a regression since 7.9.3. If you look at my blog post <https://auth0.com/blog/micro-frontends-for-java-microservices/> and search for "You can verify everything is started using Consul", you'll see that all instances are healthy. image.png (view on web) <https://github.com/jhipster/generator-jhipster/assets/17892/51dfb32b-0c78-4eb6-b0f0-08545a431378> When I tried the same steps with v8, it results in the screenshot in this issue's description. — Reply to this email directly, view it on GitHub <#24377 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIOKFZJFOHBHJGTGQL4XCLYG67R7AVCNFSM6AAAAAA75BZ77OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZSHA2TKNZXGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bassyrlakh]

Try checking the Docker network for the Consul stack and make sure that exchange to service has been checked health

[mraible]

This is now fixed on the main branch.

[mraible]

This issue has returned again on the main branch.

[github-actions]

JHipster has completed the sample check
.yo-rc.json: blank
Entities JDL: blank
Application: successfully generated
Frontend check: skipped
Backend check: skipped
E2E check: skipped

This check uses jhipster info output from the issue description to generate the sample.
Bug report that does not contain this information will be marked as invalid.

[hfsoares]

This issue is present on version 8.7.1

[mraible]

I can confirm this happens as well. I've seen it twice during my presentations this month. I'll reopen.