You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Vanjikumaran Sivajothy (JIRA)" <ji...@apache.org> on 2016/05/27 19:19:12 UTC

[jira] [Comment Edited] (SYNAPSE-1018) Migrating from Log4j 1.x to Apache Log4j 2

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

Vanjikumaran Sivajothy edited comment on SYNAPSE-1018 at 5/27/16 7:18 PM:
--------------------------------------------------------------------------

theoretically without rewriting the code base, it is possible to migrate with bridge provide in [1].  

IMO, It is that good to rewrite with the major release and utilize the native usage of log4j 2 and async capacity?

[1] https://logging.apache.org/log4j/2.x/faq.html#which_jars


was (Author: vanji@wso2.com):
theoretically without rewriting the code base, it is possible to migrate with bride provide in [1].  

IMO, It is that good to rewrite with the major release and utilize the native usage of log4j 2 and async capacity?

[1] https://logging.apache.org/log4j/2.x/faq.html#which_jars

> Migrating from Log4j 1.x to Apache Log4j 2
> ------------------------------------------
>
>                 Key: SYNAPSE-1018
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-1018
>             Project: Synapse
>          Issue Type: Improvement
>            Reporter: Vanjikumaran Sivajothy
>            Assignee: Hiranya Jayathilaka
>
> Currently synapse utilize log4j 1.2.14 as the decency. If we are able to upgrade syanpse with log4j 2, It is possible to use Asynchronous Loggers for high throughput and low latency logging.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org