Uploaded image for project: 'MariaDB Connector/J'
  1. MariaDB Connector/J
  2. CONJ-393

improve setQueryTimeout to use SET STATEMENT max_statement_time

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-RC
    • Component/s: Other
    • Labels:
      None

      Description

      Actual Statement.setQueryTimeout use one additional thread per query.
      The actual implementation create an additional thread. When timeout, a new connection will be created to permit executing a query to killing the current connection.

      Since server 10.1, MariaDB server has a command that permit server to handle that directly : https://mariadb.com/kb/en/mariadb/aborting-statements/ with command : SET STATEMENT max_statement_time=1 FOR "..."

      The solution has to be implemented.

      This has another advantage to be compatible with maxscale (existing connection is not, since the thread ID number is a fake Maxscale thread ID)

        Attachments

          Activity

            People

            Assignee:
            diego dupin Diego Dupin
            Reporter:
            diego dupin Diego Dupin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration