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 "Tiago Cardoso (JIRA)" <ji...@apache.org> on 2014/03/13 01:37:45 UTC
[jira] [Updated] (LOG4J2-565) Log4j2 loading time
[ https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tiago Cardoso updated LOG4J2-565:
---------------------------------
Description:
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){
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.
was:
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){
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.
> Log4j2 loading time
> -------------------
>
> 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){
> 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.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org