[
https://issues.apache.org/jira/browse/GEODE-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871500#comment-16871500
]
ASF subversion and git services commented on GEODE-6862:
--------------------------------------------------------
Commit 61d38975514d3d44b07a3664f504f2fb076f6261 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=61d3897 ]
GEODE-6862: Add MALFORMED_LOG4J_MESSAGE to LogConsumer
* Rename MALFORMED_I18N_MESSAGE in Patterns
* Add MALFORMED_LOG4J_MESSAGE in Patterns
* Use MALFORMED_LOG4J_MESSAGE in isExceptionErrorOrSomeSpecialCase
* Move call to isExceptionErrorOrSomeSpecialCase because all matches
in this method seem to be ignored by LogConsumer (this class is
kind of a mess)
> Fail dunit suspect string check if log output contains {}
> ---------------------------------------------------------
>
> Key: GEODE-6862
> URL: https://issues.apache.org/jira/browse/GEODE-6862
> Project: Geode
> Issue Type: Wish
> Components: tests
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> I propose adding `{}` to the dunit suspect string check. The presence of `{}`
> probably indicates a malformed Log4J log statement is missing one or more
> parameters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
