Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2017-01-26 Thread tomcat
On 24.01.2017 18:07, Farhan Tariq wrote: Hello chris, Yes we are facing the exact behavior as mentioned by you "2017-01-23 04:59:58 Something happened 2017-01-23 04:59:59 Something happened 2017-01-24 05:00:00 Something happened 2017-01-24 05:00:01 Something happened" The changes made to set

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2017-01-24 Thread Farhan Tariq
Hello chris, Yes we are facing the exact behavior as mentioned by you "2017-01-23 04:59:58 Something happened 2017-01-23 04:59:59 Something happened 2017-01-24 05:00:00 Something happened 2017-01-24 05:00:01 Something happened" The changes made to set timezone to system default only effective

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2017-01-23 Thread tomcat
On 23.01.2017 16:38, Christopher Schultz wrote: I'm curious... what's wrong with GMT? I have been wondering about that too. It seems a rather bad idea to me, as it brings potential problems of compatibility with log-exploiting programs, hosting servers somewhere else, comparing time between

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2017-01-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Farhan, On 1/21/17 2:20 AM, Farhan Tariq wrote: > hi, > > we have tomcat 7.0.68 deployed on linux. > > To capture the log in local system timezone using > ExtendedAccessLogValve class we change the following line >

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2017-01-20 Thread Farhan Tariq
hi, we have tomcat 7.0.68 deployed on linux. To capture the log in local system timezone using ExtendedAccessLogValve class we change the following line "currentTimestampFormat.setTimeZone(TimeZone.getTimeZone("GMT"))" into "currentTimestampFormat.setTimeZone(TimeZone.getDefault())" in

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2016-12-14 Thread Konstantin Kolinko
2016-12-14 18:48 GMT+03:00 Farhan Tariq : > Hello team, > > I am not sure why the timezone is explicitly set to GMT in > ExtendedAccessLogValve class? > To capture URL encoded parameters I looking to use this class but need help > to get time in GMT+5. I am using tomcat 7

Re: ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2016-12-14 Thread tomcat
On 14.12.2016 16:48, Farhan Tariq wrote: Hello team, I am not sure why the timezone is explicitly set to GMT in ExtendedAccessLogValve class? To capture URL encoded parameters I looking to use this class but need help to get time in GMT+5. I am using tomcat 7 on redhat. Any suggestions? Hi.

ExtendedAccessLogValve.class overloaded timezone and set it to GMT

2016-12-14 Thread Farhan Tariq
Hello team, I am not sure why the timezone is explicitly set to GMT in ExtendedAccessLogValve class? To capture URL encoded parameters I looking to use this class but need help to get time in GMT+5. I am using tomcat 7 on redhat. Any suggestions? Thanks Farhan