logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikael Ståldal (JIRA) <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1295) Automated testing to verify no temporary objects allocated in gc-free configuration
Date Tue, 22 Mar 2016 13:45:25 GMT

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

Mikael Ståldal commented on LOG4J2-1295:
----------------------------------------

There seems to be an error there, I had to change line 128 to this to get it to work (otherwise
the absolute pathname is missing the leading /):

        final String path = temp.substring("jar:file:".length(), temp.indexOf('!'));


> Automated testing to verify no temporary objects allocated in gc-free configuration
> -----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1295
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1295
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API, Configurators, Core, Layouts, Pattern Converters
>    Affects Versions: 2.5
>            Reporter: Remko Popma
>            Assignee: Remko Popma
>             Fix For: 2.6
>
>
> LOG4J2-1270 proposes changes to support gc-free behaviour (no allocation of temporary
objects) in certain configurations.
> This ticket is about verifying that Log4j does not allocate in these configurations.
It is not always obvious that some code creates objects, so it is easy for regressions to
creep in during maintenance code changes.
> Ideally this verification is packaged so it can run automatically during the test phase
of the build, for example in a JUnit test.



--
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


Mime
View raw message