Affects Version/s: 2.1
Fix Version/s: 2.4
Don't know if this is a documentation issue, a configuration bug, or just a user error, so I have left many fields empty in this report.
I'm trying to create an xml configuration where I have asynchronous logging to a socket, and synchronous logging to disk.
The pdf-documentation says:
"Synchronous and asynchronous loggers can be combined in configuration. This gives you more
flexibility at the cost of a slight loss in performance (compared to making all loggers asynchronous).
Use the <asyncRoot> or <asyncLogger> configuration elements to specify the loggers that need to
be asynchronous. The same configuration file can also contain <root> and <logger> elements for
the synchronous loggers."
.. so I created a configuration file that looks like this:
That configuration only leads to logging to the socket appender, and nothing to the console.
Changing the order of the root elements to:
Gives console logging, but no logging to the socket.
Changing the config to:
Gives both console and socket logging, for "com" and descendants, but code that is logging to another domain than com does not end up in the console.
I also tried to leave the name empty in the test above, but that doesn't work.
What's the problem? The documentation, or my understanding of it, or the implementation?
I would really like to have both asynchronous and synchronous root in the same configuration.