quarkus: Malformed DNS message on MacOS
Describe the bug
When starting on macOS this message is printed:
Can not find {} in the classpath, fallback to system defaults. This may result in incorrect DNS resolutions on MacOS.
Notice the {} in the final message.
Expected behavior
Message tells me what can’t be found.
Actual behavior
☝️
How to Reproduce?
Start an application in dev mode on macOS.
Output of uname -a or ver
macOS 12
Output of java -version
OpenJDK 17.0.2
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.12.0.Final
Build tool (ie. output of mvnw --version or gradlew --version)
Gradle 7.4.2
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- Bring JBossNettyLoggerFactory implementation in line with other implementations This change essentially makes all the method implementations behave in the same way Netty's built-in implementations do... — committed to geoand/quarkus by geoand 2 years ago
- Bring JBossNettyLoggerFactory implementation in line with other implementations This change essentially makes all the method implementations behave in the same way Netty's built-in implementations do... — committed to geoand/quarkus by geoand 2 years ago
- Merge pull request #27653 from geoand/#27605 Bring JBossNettyLoggerFactory implementation in line with other implementations — committed to quarkusio/quarkus by geoand 2 years ago
- Bring JBossNettyLoggerFactory implementation in line with other implementations This change essentially makes all the method implementations behave in the same way Netty's built-in implementations do... — committed to gsmet/quarkus by geoand 2 years ago
- Bring JBossNettyLoggerFactory implementation in line with other implementations This change essentially makes all the method implementations behave in the same way Netty's built-in implementations do... — committed to nenros/quarkus by geoand 2 years ago
The
JBossNettyLoggerFactoryand its corresponding logger should do the same thing that Netty’sJdkLoggerdoes and callio.netty.util.internal.logging.MessageFormatter#arrayFormat(format, arguments)to format the arguments, after doing a level check.I don’t think it’s the same issue TBH, because it looks like the Mongo driver failing to perform DNS, not Netty.
I would suggest opening a new issue - and sharing a sample application if possible.