[ 
https://issues.apache.org/jira/browse/GEODE-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664167#comment-16664167
 ] 

ASF subversion and git services commented on GEODE-5827:
--------------------------------------------------------

Commit 3d4c342af7272f9a9710f85e0ee4e4ecc1beb8fc in geode's branch 
refs/heads/feature/GEODE-5927 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3d4c342 ]

GEODE-5827: Use standard pattern converters in suspect appender (#2704)

The suspect appender is added programmatically without a log4j2.xml
so there is apparently no way to specify additional plugin packages.

Change hexTid back to tid to prevent error messages about not finding 
the HexThreadIdPatternConverter.

> DUnit suspect string setUp is generating ERROR messages
> -------------------------------------------------------
>
>                 Key: GEODE-5827
>                 URL: https://issues.apache.org/jira/browse/GEODE-5827
>             Project: Geode
>          Issue Type: Test
>          Components: tests
>            Reporter: Kirk Lund
>            Assignee: Kirk Lund
>            Priority: Trivial
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The ERROR messages are generated because hexTid is a custom PatternConverter. 
> DUnit is programmatically adding an Appender for suspect string detection and 
> there doesn't seem to be a way to add custom PatternConverter. We'll probably 
> have to use tid instead of hexTid for the suspect string detection appender.
> {noformat}
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized format specifier 
> [hexTid]
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized conversion specifier 
> [hexTid] starting at position 78 in conversion pattern.
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized format specifier 
> [hexTid]
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized conversion specifier 
> [hexTid] starting at position 78 in conversion pattern.
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier 
> [hexTid]
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier 
> [hexTid] starting at position 78 in conversion pattern.
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier 
> [hexTid]
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier 
> [hexTid] starting at position 78 in conversion pattern.
> {noformat}



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

Reply via email to