You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by "DiFrango, Ronald" <Ro...@capitalone.com> on 2017/03/13 14:19:43 UTC
EDT Transition?
All,
We’re in the EST/EDT timezone and we saw some odd behavior with our layout pattern where we had %d{DATE}. Basically, the times were reporting as EST until midnight then they properly started showing up as EDT.
The interesting thing is that when we fixed it to be %d{dd MMM yyyy HH:mm:ss,sss} it also resolved it.
Any thoughts?
Thanks,
Ron DiFrango
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: EDT Transition?
Posted by Remko Popma <re...@gmail.com>.
Ron, Shishir, all,
I've started to look at the issue.
Remko
Sent from my iPhone
> On Mar 14, 2017, at 8:34, DiFrango, Ronald <Ro...@capitalone.com> wrote:
>
> Matt,
>
> It most certainly is and my college Shishir has updated the ticket below with some details of what he thinks the root cause of the problem is.
>
> He’s willing to pitch in and help fix the issue as it’s a risk come the next Daylight savings switch.
>
> Ron DiFrango
>
> On 3/13/17, 11:34 AM, "Matt Sicker" <bo...@gmail.com> wrote:
>
> I'm guessing this is related to a bug I found yesterday in the tests:
> https://issues.apache.org/jira/browse/LOG4J2-1849
>
> On 13 March 2017 at 09:19, DiFrango, Ronald <Ro...@capitalone.com>
> wrote:
>
>> All,
>>
>> We’re in the EST/EDT timezone and we saw some odd behavior with our layout
>> pattern where we had %d{DATE}. Basically, the times were reporting as EST
>> until midnight then they properly started showing up as EDT.
>>
>> The interesting thing is that when we fixed it to be %d{dd MMM yyyy
>> HH:mm:ss,sss} it also resolved it.
>>
>> Any thoughts?
>>
>> Thanks,
>>
>> Ron DiFrango
>>
>> ________________________________________________________
>>
>> The information contained in this e-mail is confidential and/or
>> proprietary to Capital One and/or its affiliates and may only be used
>> solely in performance of work or services for Capital One. The information
>> transmitted herewith is intended only for use by the individual or entity
>> to which it is addressed. If the reader of this message is not the intended
>> recipient, you are hereby notified that any review, retransmission,
>> dissemination, distribution, copying or other use of, or taking of any
>> action in reliance upon this information is strictly prohibited. If you
>> have received this communication in error, please contact the sender and
>> delete the material from your computer.
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
> B‹KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB•È [œÝXœØÜšX™KK[XZ[ˆÙÍ‹]\Ù\‹][œÝXœØÜšX™PÙÙÚ[™Ë˜\XÚK›Ü™ÃB‘›ÜˆY][Û˜[ÛÛ[X[™ ËK[XZ[ˆÙÍ‹]\Ù\‹Z[ ÙÙÚ[™Ë˜\XÚK›Ü™ÃBƒ
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: EDT Transition?
Posted by "DiFrango, Ronald" <Ro...@capitalone.com>.
Matt,
It most certainly is and my college Shishir has updated the ticket below with some details of what he thinks the root cause of the problem is.
He’s willing to pitch in and help fix the issue as it’s a risk come the next Daylight savings switch.
Ron DiFrango
On 3/13/17, 11:34 AM, "Matt Sicker" <bo...@gmail.com> wrote:
I'm guessing this is related to a bug I found yesterday in the tests:
https://issues.apache.org/jira/browse/LOG4J2-1849
On 13 March 2017 at 09:19, DiFrango, Ronald <Ro...@capitalone.com>
wrote:
> All,
>
> We’re in the EST/EDT timezone and we saw some odd behavior with our layout
> pattern where we had %d{DATE}. Basically, the times were reporting as EST
> until midnight then they properly started showing up as EDT.
>
> The interesting thing is that when we fixed it to be %d{dd MMM yyyy
> HH:mm:ss,sss} it also resolved it.
>
> Any thoughts?
>
> Thanks,
>
> Ron DiFrango
>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>
--
Matt Sicker <bo...@gmail.com>
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: EDT Transition?
Posted by Matt Sicker <bo...@gmail.com>.
I'm guessing this is related to a bug I found yesterday in the tests:
https://issues.apache.org/jira/browse/LOG4J2-1849
On 13 March 2017 at 09:19, DiFrango, Ronald <Ro...@capitalone.com>
wrote:
> All,
>
> We’re in the EST/EDT timezone and we saw some odd behavior with our layout
> pattern where we had %d{DATE}. Basically, the times were reporting as EST
> until midnight then they properly started showing up as EDT.
>
> The interesting thing is that when we fixed it to be %d{dd MMM yyyy
> HH:mm:ss,sss} it also resolved it.
>
> Any thoughts?
>
> Thanks,
>
> Ron DiFrango
>
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>
--
Matt Sicker <bo...@gmail.com>