[CAMEL-14632] Optimization of DefaultExchangeFormatter leeds to crapy log output

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.0
• Fix Version/s: 3.2.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Benjamin Graf
• Created: 29/Feb/20 15:29
• Updated: 02/Mar/20 08:53
• Resolved: 02/Mar/20 08:53

Description

The changes to DefaultExchangeFormatter from issue CAMEL-14354 have an "ugly" side effect. If using multiline logging and StringBuffer is less than 10000 chars you'll get a String logged with lots of ###REPLACE_ME###.

Reproduce with test case Camel14632Test.java and see log output
e.g.:

2020-02-29T16:25:58,966 INFO  [main            ] test                             - Exchange[###REPLACE_ME###  Id: ID-PC47376-1582989958950-0-1###REPLACE_ME###  ExchangePattern: InOnly###REPLACE_ME###  Properties: {CamelToEndpoint=log://test?multiline=true&showAll=true}###REPLACE_ME###  Headers: {}###REPLACE_ME###  BodyType: String###REPLACE_ME###  Body: test]

Issue Links

• is caused by: CAMEL-14354 camel-core - Optimize unnecessary object allocations