Quarkus - Microcks only uses port 8081 in Dev Mode

[vleon1a]

Hello everyone!
I am integrating Microcks in my Quarkus applications, and I faced an issue when running my applications in Dev Mode, running the OPEN API SCHEMA runner. Basically, Microcks fails to connect to the application, as it is exposed by default on port 8080 in Dev Mode, while the Microcks extension exposes only the port 8081 to Testcontainers.
I took the liberty to raise an issue microcks/microcks-quarkus#204 and PR microcks/microcks-quarkus#208 to address this.
I just wanted to make sure this change is making sense?
Thanks

[lbroudoux]

Hi @vleon1a
Sorry for the delay, and thanks for your patience. I need to deep dive again into this but IIRC there is some constraint in the Quarkus Lifeycle that prevents the Dev Services from retrieving the dynamic port that is used to start the Quarkus app ...

[vleon1a]

Hello @lbroudoux !
No worries at all 😃
Indeed, the dynamic port allocation is a bit tricky, which is why I just proposed applying a simple fix for the most common case, where we open quarkus.http.port on top of quarkus.http.test-port.

[lbroudoux]

0.4.4 versions of Microcks-Quarkus has just been released and included your PR. Thanks!

[vleon1a]

Thanks @lbroudoux ! I validated the fix today, Microcks can now reach the application on both port 8080 in dev mode, and 8081 in test mode 👍