[BUG] Base64 encoder in response body corrupted info with huge 'A' chunks in Tuple JSON logger

[ParvelAWS]

What is the bug?

In some of the replay message test, Tuple JSON logger wrote the replayed response with a corrupted base64 encode of the body section, usually with a lot of 'A' for over 5MB

How can one reproduce the bug?

Replay a ELB health check traffic with GET / towards OpenSearch clusters

What is the expected behavior?

Correct base64 encoded response body in JSON

What is your host/environment?

EKS with AWS Linux 2023 min, AWS JDK17.

Do you have any screenshots?

Do you have any additional context?

Add any other context about the problem.

[gregschohn]

Thanks for filing this issue. The above referenced PR should solve this issue (in commit 6a02317).

Please verify or open any new bugs if you find anything else amiss.