Skip to content

Conversation

@claudiamurialdo
Copy link
Collaborator

Log4net uses thread name for pattern %thread when available. It uses the thread number if no name is available.
In .NET Framework and .NET until v5 threadpool threads are not named by default, therefore thread number is printed in logs by default, but in Net6 they are named.
Given that the thread number is more useful that thread name, the property threadid is added to log4net context and can be used with the pattern [%property{threadid}]
Issue:101981

…tead of thread name in log messages.

log4net uses thread name for pattern %thread when available, and it uses the thread number if no name is available.
In .NET Framework and .NET until v5  threadpool threads are not named by default, therefore thread number is printed in traces by default, but in Net6 they are named.
For tracing the thread number is more useful that thread name.
@genexusbot
Copy link
Collaborator

Cherry pick to beta success

@claudiamurialdo claudiamurialdo temporarily deployed to external-storage-tests March 21, 2023 17:29 — with GitHub Actions Inactive
ggallotti
ggallotti previously approved these changes Mar 21, 2023
@genexusbot
Copy link
Collaborator

Cherry pick to beta success

@claudiamurialdo claudiamurialdo temporarily deployed to external-storage-tests March 21, 2023 18:00 — with GitHub Actions Inactive
@claudiamurialdo claudiamurialdo merged commit f89fd7c into master Mar 23, 2023
@claudiamurialdo claudiamurialdo deleted the log4net-thread-id branch March 23, 2023 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants