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

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

Looks like my analysis was incorrect or incomplete. To be clear, the load time 
you are experiencing is not normal. I think a normal load time is like 100-150 
milliseconds.

Still, for some reason the plugin manager is taking a long time locating the 
log4j plugins... Two questions to help us try to reproduce the issue: do you 
have any custom log4j plugins, or does your log4j2.xml configuration have a 
value in the {{packages}} attribute? For example:
{code}
<Configuration status="trace" packages="my.company.myplugins"> <!-- do you have 
anything like this? -->
...
{code}
Also, could you tell us what you see when you print 
{{System.out.println(System.getProperty("java.class.path"));}} ?

> 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){
>     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.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to