Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/218
No worries, thank you for your feedback as always!
We might want to consider updating `ReusableMessageFactory.newMessage(final
String message, final Object... params)` to return a non-reusable
ParameterizedMessage instance. It seems like a bug that logging an object array
may result in that array being mutated the next time an event is logged on the
same thread. It's unfortunate that we cannot differentiate between an array
passed as a value, and an array created by a varargs invocation.
Thoughts?
---
