1 of 1 people found this helpful
Resolved by adding adjusted JVM argument from main startup script (standalone.bat / standalone.sh)
-Djava.util.logging.manager=org.jboss.logmanager.LogManager is always required for embedded container, it doesn't start otherwise.
JBoss Logging Manager needs to be configured before start though using -Dlogging.configuration
Thanks, this helped a lot!
One minor addition: The file "%JBOSS_CONFIG_DIR%/logging.properties" is usually generated by Wildfly standalone during startup, based on the information configured within "%JBOSS_CONFIG_DIR%/standalone[-full].xml". Since access to the config file specified may preceed the generation of this file (as was the case for me when letting Maven's failsafe-plugin start Wildfly Embedded) it might not get picked up at all. I worked around this (a bit hackish...) by
- copying a generated version of "logging.properties" into src/test/resources
- letting the location of "server.log" get injected via Maven resource plugin's filtering option
- specify the filtered "logging.properties" via failsafe plugin as described above.
That way all log entries were going into server.log from the beginning, including Wildfly's startup logging.