You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "John Meikle (Jira)" <ji...@apache.org> on 2021/08/23 19:24:00 UTC
[jira] [Updated] (LOG4J2-3142) Timestamp always returns 0 for
LogEventAdapter
[ https://issues.apache.org/jira/browse/LOG4J2-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Meikle updated LOG4J2-3142:
--------------------------------
Description:
When invoking {{LogEventAdapter.getTimestamp()}} the result is always 0 even if the {{LogEvent}} used in construction contains a timestamp.
Should consider overriding the method to return {{LogEvent.getTimeMillis()}} which represents the same thing.
was:
When invoking `LogEventAdapter.getTimestamp()` the result is always 0 even if the `LogEvent` used in construction contains a timestamp.
Should consider overriding the method to return `LogEvent.getTimeMillis()` which represents the same thing.
> Timestamp always returns 0 for LogEventAdapter
> ----------------------------------------------
>
> Key: LOG4J2-3142
> URL: https://issues.apache.org/jira/browse/LOG4J2-3142
> Project: Log4j 2
> Issue Type: Bug
> Components: log4j 1.2 emulation
> Affects Versions: 2.14.1
> Reporter: John Meikle
> Priority: Minor
>
> When invoking {{LogEventAdapter.getTimestamp()}} the result is always 0 even if the {{LogEvent}} used in construction contains a timestamp.
> Should consider overriding the method to return {{LogEvent.getTimeMillis()}} which represents the same thing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)