[
https://issues.apache.org/jira/browse/LOG4J2-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933434#comment-13933434
]
Gary Gregory edited comment on LOG4J2-565 at 3/13/14 3:49 PM:
--------------------------------------------------------------
I added more information to our logging.
Old:
{noformat}
Generated plugins in 6.386125544 seconds
{noformat}
New:
{noformat}
Generated plugins in 6.386125544 seconds, packages: {list,of,packages},
preload: {true|false}.
{noformat}
was (Author: garydgregory):
I added more information to our logging.
Old:
Generated plugins in 6.386125544 seconds
New:
Generated plugins in 6.386125544 seconds, packages: {list,of,packages},
preload: {true|false}.
> 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]
