[
https://issues.apache.org/jira/browse/GEODE-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Martell updated GEODE-10016:
------------------------------------
Description:
The native client logging system currently prints the threadId in all log
messages. Since all internally created native client threads are named, we
should print the threadName instead of threadId. This will be extremely helpful
to understanding the flow of messages since there are many background threads
in the native client.
Note: Lots of log messages are running on an application thread which was not
created internally by the native client. Messages running on these threads
should continue to print the threadId.
was:
The native client logging system currently prints the threadId in all log
messages. Since all internally created native client threads are named, we
should print the threadName instead of threadId.
Note: Lots of log messages are running on an application thread which was not
created internally by the native client. Messages running on these threads
should continue to print the threadId.
Priority: Minor (was: Major)
> Use Thread Name In Log Messages
> -------------------------------
>
> Key: GEODE-10016
> URL: https://issues.apache.org/jira/browse/GEODE-10016
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Michael Martell
> Priority: Minor
>
> The native client logging system currently prints the threadId in all log
> messages. Since all internally created native client threads are named, we
> should print the threadName instead of threadId. This will be extremely
> helpful to understanding the flow of messages since there are many background
> threads in the native client.
> Note: Lots of log messages are running on an application thread which was not
> created internally by the native client. Messages running on these threads
> should continue to print the threadId.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
