I fixed the only problem I could find last week. However, we still have more to do as we really need to support the StackWalker API and the “right” way to do it would require massive changes. I also need to benchmark the cost of invoking the StackWalker API to return the method’s caller to see what the impact would be to do it on every logging call.
Ralph > On Feb 6, 2017, at 9:15 AM, Matt Sicker <boa...@gmail.com> wrote: > > I remember Ralph mentioned that he tested it out and found that it worked > pretty well. See issue: <https://issues.apache.org/jira/browse/LOG4J2-1359 > <https://issues.apache.org/jira/browse/LOG4J2-1359>> > > On 6 February 2017 at 09:56, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > I haven't had a chance to look at this yet, but is the new stack walking API > in Java 9 of any use for us? I believe applications/libraries like Log4j were > supposed to be the drivers behind this feature, but last time I checked they > were not going to cater for our use case (inspect the stack from the bottom > up)... > > From a functional point of view, is anybody aware of anything outstanding we > need to fix for Log4j 2 to work correctly on Java 9? > > Remko > > > > -- > Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
