Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.3.0-alpha4
-
None
-
Windows 10 Pro
Description
When using SocketAppender as the only appender for a certain Logger the threadName from the logging event is not evaluated in the calling thread as expected but in the writing thread which does the serialization. This leads to a wrong threadName on consumer side.
If there are other appenders attached to a certain logger, the threadName is resolved and cached in the LoggingEvent in the calling thread and so it is correct.