GitHub user ppkarwasz added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
> But can you think of scenarios where this may occur ?
In version `2.21.0`, the parameter formatting logic was changed to **strictly
enforce** a match between `{}` place
GitHub user arbardhan added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
2.24.3 is not available under our org enterprise distribution yet - pending
approval. We only go back to older versions. But can you think of scenarios
where this may occ
GitHub user ppkarwasz added a comment to the discussion: Parameterized Info
intermittently throws IllegalArgumentException
@arbardhan,
Did you test with the latest release (`2.24.3`)?
GitHub link:
https://github.com/apache/logging-log4j2/discussions/3695#discussioncomment-13288046
This
Hi Volkan,
On 27.05.2025 11:57, Volkan Yazıcı wrote:
> I haven't been feeling well for a while. Could I have one more week to work
> on the remaining work assigned to me, please?
I'm really sorry to hear you haven't been feeling well—please take all
the time you need to rest and recover. Your hea
GitHub user arbardhan edited a discussion: Parameterized Info intermittently
throws IllegalArgumentException
I log 8 parameters using {} in log.info this comes from a httpServlet request
preHandlePath. This log statement sometimes throwa IAE exception stating only 5
arguments provided for 8 p
I haven't been feeling well for a while. Could I have one more week to work
on the remaining work assigned to me, please?
On Fri, May 16, 2025 at 5:37 PM Piotr P. Karwasz
wrote:
> Hi all,
>
> I'm aiming to release Log4j 2.25.0 before the end of the month, with a
> release candidate planned for n