logging-manager-ui not working in native-image build on linux x86 about quarkus-logging-manager

[phillip-kruger]

Thank for the reproducer. I managed to recreate, so looking at it now. This might need a new version of Logging manager.

[phillip-kruger]

@ansgerl Please try with the just released 2.1.1 and let me know. thanks

[phillip-kruger]

Bug :) We always create a new FileSystem, but sometime it exists. Seems like some gradle specific issue, could be that they cache or something.

[ansgerl]

Thanks very much!

[phillip-kruger]

Does it work in JVM mode (so not Dev Mode, running the jar) ?

[ansgerl]

Your right, it does also not work in JVM production mode.
How can I build it, so it also works in production mode?

[phillip-kruger]

How does your application.properties look like ?
Do you have : quarkus.logging-manager.ui.always-include=true

(see
https://github.com/phillip-kruger/logging-manager-example/blob/3da526463bad714453b1881d5a0121bde4d9221e/src/main/resources/application.properties#L5 )

[ansgerl]

O.k. with this I get a new error when building:

io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[error]: Build step io.quarkiverse.loggingmanager.deployment.LoggingManagerProcessor#includeUiAndWebsocket threw an exception: java.nio.file.FileSystemAlreadyExistsException
at jdk.zipfs/jdk.nio.zipfs.ZipFileSystemProvider.newFileSystem(ZipFileSystemProvider.java:102)
at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:337)
at java.base/java.nio.file.FileSystems.newFileSystem(FileSystems.java:286)
at io.quarkiverse.loggingmanager.deployment.LoggingManagerProcessor.addStaticResource(LoggingManagerProcessor.java:344)
at io.quarkiverse.loggingmanager.deployment.LoggingManagerProcessor.includeUiAndWebsocket(LoggingManagerProcessor.java:203)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at io.quarkus.deployment.ExtensionLoader$2.execute(ExtensionLoader.java:820)
at io.quarkus.builder.BuildContext.run(BuildContext.java:277)
at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.jboss.threads.JBossThread.run(JBossThread.java:501)

[phillip-kruger]

OK that is interesting. Do you have a small reproducer I can look at ?

[ansgerl]

The funny thing is: when started via quarkusDev it runs, but when building production jar, build fails.

These are the application.properties I use:

#GLOBAL configuration
quarkus.http.port=4020
quarkus.banner.path=banner.txt
quarkus.health.openapi.included=true
quarkus.default-locale=en-US
quarkus.smallrye-openapi.path=/swagger
mp.openapi.scan.disable=true
quarkus.swagger-ui.always-include=true
quarkus.swagger-ui.path=/swagger-ui

Add the logging manager openapi

quarkus.logging-manager.ui.always-include=true
quarkus.logging-manager.openapi.included=true

quarkus.native.additional-build-args=-H:ResourceConfigurationFiles=XXX,-H:Log=registerResource:
quarkus.native.auto-service-loader-registration=false
#New with Quarkus 1.11 - native-image minimum available log level
quarkus.log.min-level=DEBUG

Use file rotation to avoid out of memory issues

quarkus.log.file.rotation.max-file-size=10M
quarkus.log.file.rotation.max-backup-index=10

%prod.quarkus.log.console.enable=false

[ansgerl]

When building this project on a iMac (intel) using ./gradlew build I get the above error.

code-with-quarkus 3.zip

Maybe it is a gradle issue?

I am using Java 11.

[ansgerl]

It now works! Thanks!
What was the problem?