You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2018/12/19 09:07:11 UTC

[Bug 63018] New: When there is a time field in the query result, the time is automatically increased by 13 hours

https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

            Bug ID: 63018
           Summary: When there is a time field in the query result, the
                    time is automatically increased by 13 hours
           Product: JMeter
           Version: 5.0
          Hardware: PC
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: face_211@126.com
                CC: face_211@126.com
  Target Milestone: JMETER_5.0

Created attachment 36336
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36336&action=edit
Database data query results

Query database data through jdbc request
When the query result contains a time field, the query result program
automatically adds 13 hours.

test environment
Win10 , jmeter 5.0 , current application time zone CST

Test procedure
1. Add jdbc request and enter the query script.
2. Add View the result tree and execute the script
3. View the results
4. Query database data through jdbc request
When the query result contains a time field, the query result program
automatically adds 13 hours.

See the attached map for details
The jmeter database query result time is greater than the database actual
database storage time.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63018] When there is a time field in the query result, the time is automatically increased by 13 hours

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
             Status|NEW                         |NEEDINFO
                 OS|                            |All
           Severity|blocker                     |normal

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
What is the database you're using ?
What is its timezone ?
What is the type of field you store time in ?


You might want to read this:

https://blog.jooq.org/2015/06/30/whats-even-harder-than-dates-and-timezones-dates-and-timezones-in-sql-jdbc/

I don't think there is any issue with JMeter here, possibilities are:

- wrong type to store time, dropping timezone information
- timezone mismatch between jmeter machine/jvm and database server

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63018] When there is a time field in the query result, the time is automatically increased by 13 hours

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

--- Comment #4 from joanchen <fa...@126.com> ---
I tried jdbc request on Oracle via jmeter. The Oracle database also has the
concept of time zone, but the query result did not receive the impact of the
database time zone. @Philippe Mouawad

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63018] When there is a time field in the query result, the time is automatically increased by 13 hours

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |WORKSFORME
   Target Milestone|JMETER_5.0                  |JMETER_5.1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63018] When there is a time field in the query result, the time is automatically increased by 13 hours

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

--- Comment #2 from joanchen <fa...@126.com> ---
First thank you for your reply
However, this did not solve the problem I raised.

1, the server is centos 7, the system time zone is CST
[root@585348511cc5 /]# timedatectl
       Local time: Thu 2018-12-20 11:01:48 CST
   Universal time: Thu 2018-12-20 03:01:48 UTC
         RTC time: n/a
        Time zone: Asia/Shanghai (CST, +0800)
      NTP enabled: n/a
NTP synchronized: no
  RTC in local TZ: yes
       DST active: n/a


2, the database used by the program is mysql, version 5.7.22
3, the time field type is datetime

There is also mysql installed in the docker container, the host time is

[root@crh224 ~]# timedatectl
       Local time: four 2018-12-20 10:36:16 CST
   Universal time: four 2018-12-20 02:36:16 UTC
         RTC time: four 2018-12-20 02:36:16
        Time zone: Asia/Shanghai (CST, +0800)
      NTP enabled: no
NTP synchronized: yes
  RTC in local TZ: no
       DST active: n/a

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63018] When there is a time field in the query result, the time is automatically increased by 13 hours

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63018

--- Comment #3 from joanchen <fa...@126.com> ---
thank you very much for your help.

I did not expect mysql has its own time zone concept

After modifying the time zone of mysql, the jmeter query data time is normal.

-- 
You are receiving this mail because:
You are the assignee for the bug.