Assuming the default pattern for the console output it looks like your category should be XmlImportFileWatcherService not de.kairos.centraxx.model.service.xmlimport.impl.XmlImportFileWatcherService.
James R. Perkins
unfortunately that is not the solution.
Unfortunately this also does not work. And the preconfigured loggers for "server.log" do not use async-handler tags either. But thank you very much for the link, wich is quite interesting anyway...
Ok, the log4j.xml in the web application is the problem. But even if I use a log4j.xml with no configuration, the Wildfly logging properties in the standalone.xml seem to be ignored.
Does an application specific log4j.xml disable any application related logging that is configured in the application server?
I found the answer here: How To - WildFly 8 - Project Documentation Editor
How do I use log4j.properties or log4j.xml instead of using the logging subsystem configuration?
First note that if you choose to use a log4j configuration file, you will no longer be able to make runtime logging changes to your deployments logging configuration.
If that is acceptable you can use per-deployment logging and just include a configuration file in your deployment.