You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2015/10/18 16:04:05 UTC

[jira] [Commented] (LOG4J2-565) Log4j2 loading time on single-board (embedded) computers

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

Remko Popma commented on LOG4J2-565:
------------------------------------

Is this still a problem? Various improvements have been made since this was reported. Can you try again with 2.4.1?

> Log4j2 loading time on single-board (embedded) computers
> --------------------------------------------------------
>
>                 Key: LOG4J2-565
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-565
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.0-rc1
>         Environment: Using ejre1.6.0_25 in an ARM926EJ-S rev 5 (v5l)
>            Reporter: Tiago Cardoso
>
> Everything runs fine on the Desktop computer, but the embedded system struggles to obtain the Logger.
> It takes 17 seconds just to run this line:
> Logger logger = LogManager.getLogger("testLogger");
> The classpath is empty and the whole applications is just:
> public static void main(String[] arg){
>     System.out.println("Starting application:" + System.currentTimeMillis());
>     Logger logger = LogManager.getLogger("testLogger");
>     logger.trace("Going to leave application." + System.currentTimeMillis());
>     System.exit(1);
> }
> The same system is able to run a client graphic application without this kind of event.



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

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