[jira] [Commented] (LOG4J2-2649) Is Log4j2 considered to support successful static compilation under GraalVM?

["Romain Manni-Bucau (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124975#comment-17124975 ] 

Romain Manni-Bucau commented on LOG4J2-2649:
--------------------------------------------

One issue I noted with log4j2 is that it uses a lot of static init which means most of the dependency must be init at build time, loosing all the dynamic configuration of the framework. Can be more elegant to use the lifecycle of log4j to do that and limit a lot the static init to bootstrap SPI binding - it is also a good practise to be able to stop/restart properly the *factories IMHO.

>  Is Log4j2 considered to support successful static compilation under GraalVM?
> -----------------------------------------------------------------------------
>
>                 Key: LOG4J2-2649
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2649
>             Project: Log4j 2
>          Issue Type: New Feature
>            Reporter: YangGuanchao
>            Priority: Blocker
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Oracle released GraalVM [https://github.com/oracle/graal] to support the static compilation of Java applications to Native Image, which can increase the startup speed of Java by at least 10 times. In the cloud native field, this basic technology is believed to be in the near future. Will be supported by more and more vendors, such as the Spring/Spring Boot community has supported or plans to support the feature of GraalVM, see this issue: [https://github.com/spring-projects/spring-framework/search?q=Graalvm&type=Issues] can support static compilation, so it is recommended that Log4j2 also need to support static compilation as soon as possible, and can be compiled correctly under GraalVM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)