#188 Regression: Can't start WildFly
YAJSW 13.02 fails to start WildFly. The exact same setup (same WildFly, same YAJSW config) works with YAJSW 12.16. This issue was discovered using WildFly 26.0.1 and AdoptOpenJDK 11.0.10 on Windows 10 Pro 21H1 x64.
When started on 13.02, WildFly makes the following complaint:
22-02-23 14:53:19|INFO|22108/0|22-02-23 14:53:19|WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
This complaint comes from jboss-modules. You can see the exact code here. The text is somewhat misleading. What actually happens is that it sets the "java.util.logging.manager" system property and then calls LogManager.getLogManager() to check that the desired LogManager was actually installed. The check fails and prints that warning, which isn't fatal at that point, but some other code elsewhere makes the same check later on and that check is fatal.
So I think the problem here is that something in YAJSW's wrapper is triggering the JDK logging system to initialize, and thus jboss-modules can't install its own LogManager later on. If so, any other application that tries to install its own LogManager will also have problems.
thanks for posting the issue.
i am able to reproduce it and will have an updated release in the next days.