logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1485) File size parsing is inconsistent and unnecessarily restrictive
Date Wed, 27 Jul 2016 21:30:21 GMT

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

Gary Gregory commented on LOG4J2-1485:
--------------------------------------

Thank you for your report.

Are you able to provide a patch with unit tests?

Thank you,
Gary

> File size parsing is inconsistent and unnecessarily restrictive
> ---------------------------------------------------------------
>
>                 Key: LOG4J2-1485
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1485
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.6.2
>            Reporter: Anthony Baldocchi
>            Priority: Minor
>         Attachments: optionconverter.patch
>
>
> There are (as far as I've encountered) 2 ways to parse a size from String:
> FileSize.parse(final String string, final long defaultValue)
> OptionConverter.toFileSize(final String value, final long defaultValue)
> These two implementations are not consistent with each other:
> FileSize.parse() when passed in a floating point value will silently truncate the floating
point portion to the lower long.
> OptionConverter.toFileSize() when passed in a floating point value will log an error
to the StatusLogger and return the defaultValue.
> Neither option supports units larger than GB, though multi-TB disks are common.



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