Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unrecognized configuration key "quarkus.native.jmxserver.included" was provided #46692

Open
zakkak opened this issue Mar 10, 2025 · 4 comments · May be fixed by #46699
Open

Unrecognized configuration key "quarkus.native.jmxserver.included" was provided #46692

zakkak opened this issue Mar 10, 2025 · 4 comments · May be fixed by #46699
Assignees
Labels

Comments

@zakkak
Copy link
Contributor

zakkak commented Mar 10, 2025

Describe the bug

#46592 results in the warning in the $title being thrown.

Expected behavior

Native builds should succeed without warnings

Actual behavior

Native builds print the following warning

00:53:09,694 WARN  [io.qua.config] Unrecognized configuration key "quarkus.native.jmxserver.included" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo 

How to Reproduce?

Build a native image with latest Quarkus

Output of uname -a or ver

No response

Output of java -version

No response

Mandrel or GraalVM version (if different from Java)

No response

Quarkus version or git rev

d84d1e8

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@zakkak zakkak added area/native-image kind/bug Something isn't working labels Mar 10, 2025
Copy link

quarkus-bot bot commented Mar 10, 2025

/cc @Karm (native-image), @galderz (native-image), @radcortez (config)

@zakkak
Copy link
Contributor Author

zakkak commented Mar 10, 2025

@roberttoyonaga unfortunately #46592 introduced the following warning:

00:53:09,694 WARN  [io.qua.config] Unrecognized configuration key "quarkus.native.jmxserver.included" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo 

We need to either use a different property, not under quarkus.native.jmxserver, or have Quarkus aware of it.

cc @gsmet @geoand wdyt would be the best approach (thinking about consistency)?

@geoand
Copy link
Contributor

geoand commented Mar 10, 2025

Seems to me we should just add a jmxserver config group under native config

@zakkak zakkak self-assigned this Mar 10, 2025
@radcortez
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants