Why does EAP 7.0 out of the box fail to initialize logging properly (windows)?

[mmaslak]

you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager"

I've viewed this problem all the way back from EAP 6 through versions of AS 7 until AS 7 update 10 had a fix. But EAP 7.0 seems to have regressed: I am getting the same error

I've tried the fixes that were recommended in the past, but I'm having trouble:

"JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager"

Can someone please offer the correct solution to kick off logging in Redhat JBoss EAP 7.0?

[ctomc]

there is no "known" issue with that on windows.

It could only happen if you use some kind of javaagent or have something really screwed with your environment.

[mmaslak]

Yep. A simple wrapper script that set the JAVA_HOME and JBOSS_HOME so I could have JBoss EAP 5.1 and 7.0 running concurrently was the culprit. The same script also read a couple of properties files that caused no problem in Wildfly 9 when I was porting some of our code over earlier this year in prep for the EAP GA release.

Thanks Tomaz.