I have no control over this. I think this is a general problem with third
party objects and toString(). There is no toString(fromHereToThere) or
toStringReader() so I can't see a general way to deal with it. Even if I
created a wrapper for the Object and called toString(), truncated and
cached the
OK. The only good way to handle that is to parse the YAML/JSON file while
streaming it and extract just the fields you want to include in the logs.
Ralph
> On Jan 25, 2024, at 6:40 PM, Gary Gregory wrote:
>
> Well, it's worse than that because the object is an object created by
> parsing a YAM
Well, it's worse than that because the object is an object created by
parsing a YAML (or JSON) file, then the toString() of that object
renders a String in some other format.
Gary
On Thu, Jan 25, 2024 at 7:45 PM Ralph Goers wrote:
>
> Volkan & Matt,
>
> Neither of those is going to help. The iss
Volkan & Matt,
Neither of those is going to help. The issue is that when the toString method
is called it reads a whole file in and stores it as a String. This could cause
the OOM error. Truncating it in a layout simply limits how much of the String
is printed. Even Gary’s proposal of calling s
*[Just responding to Matt. I don't have an answer for Gary.]*
`JsonTemplateLayout` has `maxStringLength`, and related with it,
`truncatedStringSuffix`.
On Thu, Jan 25, 2024 at 9:45 PM Matt Sicker wrote:
> You can use the %maxLength{…}{N} pattern converter with PatternLayout at
> least. Unfortun
You can use the %maxLength{…}{N} pattern converter with PatternLayout at least.
Unfortunately, I don’t think any other layouts support a similar option.
> On Jan 25, 2024, at 10:55, Gary D. Gregory wrote:
>
> Hi All,
>
> I'd like to ask how to if we can devise advice around an issue I ran into
Obvious mistake:
logger.debug("This is fun", myFunObject::toString)
->
logger.debug("This is fun {}", myFunObject::toString)
Gary
On Thu, Jan 25, 2024, 11:55 AM Gary D. Gregory wrote:
> Hi All,
>
> I'd like to ask how to if we can devise advice around an issue I ran into
> this week.
>
> One
Hi All,
I'd like to ask how to if we can devise advice around an issue I ran into this
week.
One of our test suites processes about 40K files of test fixtures. These inputs
are parsed, processed, and asserted. This randomly fails on a call to
Logger#debug(), randomly in that it happens usually
