[jira] [Resolved] (LOG4J2-3551) TimeBasedTriggeringPolicy time zone bug

["Ralph Goers (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers resolved LOG4J2-3551.
---------------------------------
    Resolution: Duplicate

Closing as duplicate of LOG4J2-1631

> TimeBasedTriggeringPolicy time zone bug
> ---------------------------------------
>
>                 Key: LOG4J2-3551
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3551
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API, Core, JUL adapter, Log4j-to-SLF4J
>    Affects Versions: 2.18.0
>            Reporter: NamHyoekJoon
>            Priority: Major
>
> First of all, I'm not sure if this is a bug or not.
> I want the on-time rollover to be done using a TimeBasedTriggeringPolicy .
> So I used %\{yyyy-MM-dd} and the interval is 1.
> This is known as the standard for rollover on the hour.
> But the problem is that the server time is in UTC, so I used \{GMT+09:00} to match my timezone and the output time is correct.
> However, in one of my output logs, the log of 2022-07-12 23:55 and
> Logs from 2022-07-13 00:00 coexist.
> Watching it that way, the rollover is performed at 09:00 in the morning.
> I expected it to be affected by the timezone I set, and changed it to GMT+06:00 as a test.
> My expectation was to roll over at 06:00 AM, but the result still rolls over at 09:00.
> is this a bug? what did i set wrong?
> What timezone is the TimeBasedTriggeringPolicy affected by?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)