You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2018/09/28 21:33:00 UTC

[jira] [Resolved] (GEODE-5776) Console log statements show thread id in decimal format

     [ https://issues.apache.org/jira/browse/GEODE-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund resolved GEODE-5776.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

> Console log statements show thread id in decimal format
> -------------------------------------------------------
>
>                 Key: GEODE-5776
>                 URL: https://issues.apache.org/jira/browse/GEODE-5776
>             Project: Geode
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The console log statements for stdout should show thread id in hex format, but they are now showing it in decimal format.
> Geode contains ThreadIdPatternConverter which formats the tid in hex format. Log4j2 introduced its own ThreadIdPatternConverter in 2.6 and because the Plugin name and ConverterKeys are the same, it's now being used instead of the one in Geode.
> The fix will require us to rename our Plugin and ConverterKeys.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)