On 2019/01/28 21:40:09, Remko Popma wrote:
> This reminds me of a JIRA ticket that Ralph raised.
> https://issues.apache.org/jira/browse/LOG4J2-1137
>
> That would be very nice to have!
>
> Remko.
>
> (Shameless plug) Every java main() method deserves http://picocli.info
>
> > On Jan 29,
On 2019/01/28 21:23:00, Matt Sicker wrote:
> I like the idea in general, though I wonder if this is already doable
> with an existing plugin?
>
> On Mon, 28 Jan 2019 at 04:43, 于得水 wrote:
> >
> > Hello, Log4j developers
> > We have a problem when debugging an online production system. Ou
I sent a reply mentioning the same Jira issue yesterday but for some reason it
doesn’t appear to have made it to the mailing list.
Ralph
> On Jan 28, 2019, at 2:40 PM, Remko Popma wrote:
>
> This reminds me of a JIRA ticket that Ralph raised.
> https://issues.apache.org/jira/browse/LOG4J2-113
This reminds me of a JIRA ticket that Ralph raised.
https://issues.apache.org/jira/browse/LOG4J2-1137
That would be very nice to have!
Remko.
(Shameless plug) Every java main() method deserves http://picocli.info
> On Jan 29, 2019, at 6:23, Matt Sicker wrote:
>
> I like the idea in general,
I like the idea in general, though I wonder if this is already doable
with an existing plugin?
On Mon, 28 Jan 2019 at 04:43, 于得水 wrote:
>
> Hello, Log4j developers
> We have a problem when debugging an online production system. Our
> production system manages and distributes data across mult
Hello, Log4j developers
We have a problem when debugging an online production system. Our
production system manages and distributes data across multiple worker
machines. There's a bug that can cause data unbalanced placement or even
unavailable under heavy work load. In this scenario, DEBUG l
