Connect to the server with CLI to check the settings. The OS should have nothing to do with these settings so it's more likely something just isn't configured correctly.
Here's how you could check the attributes on a standalone server:
If they are set to true you can change them with the follow CLI commands:
/subsystem=logging:write-attribute(name=add-logging-api-dependencies, value=false) /subsystem=logging:write-attribute(name=use-deployment-logging-config, value=false)
It's always best to use some kind of management client to make changes rather than editing the raw XML files.
Another option would be to use a jboss-deployment-structure.xml to exclude the logging subsystem. The two attributes above are global so they apply to all deployments. Using the jboss-deployment-structure.xml allows you choose which deployments would be processed by the logging subsystem.
James R. Perkins
Thanks James. The reason I put it in standalone.xml is that I do want it applied globally. When queried, both values are correct based on the settings.
I found conflicting jars were causing the issue. I have to think the class loading is different and that's why it worked on Windows.