Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-285

When use maxscale-1.0.5, the java connection will not disconnect when set MaxAge.

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 1.0.5
    • 1.0.5
    • mariadbclient
    • Linux 2.6.32-504.23.4.el6.x86_64 #1 SMP Tue Jun 9 20:57:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

    Description

      When use maxscale-1.0.5, the java connection will not automatically disconnect when set MaxAge.

      In tomcat connection pool , we set MaxAge=1200, when directly connect to DB, the connection will automatically be disconnected every 20 minutes. But use MaxScale to connect DB, the connection will always connect.
      The program will get error message when the connection is disconnected by Firewall or MySQL.
      Please help check how to fix this problem.

      Attachments

        Activity

          Descending order - Click to sort in ascending order
          johan.wikman Johan Wikman added a comment -

          Reported for a very old version and as we have not received more information it is closed as incomplete.

          johan.wikman Johan Wikman added a comment - Reported for a very old version and as we have not received more information it is closed as incomplete.
          markus makela markus makela added a comment -

          caisunny Could retest this with the 1.2 version of MaxScale?

          markus makela markus makela added a comment - caisunny Could retest this with the 1.2 version of MaxScale?
          markus makela markus makela added a comment -

          Does tomcat explicitly close the connections when MaxAge is exceeded? If the connections are not closed, adding the connection_timeout=<time> parameter should close connections once the time is exceeded. This parameter is supported starting from version 1.1.

          If the connections are closed by closing the socket or sending a COM_QUIT packet, this does seem to be a valid bug.

          markus makela markus makela added a comment - Does tomcat explicitly close the connections when MaxAge is exceeded? If the connections are not closed, adding the connection_timeout=<time> parameter should close connections once the time is exceeded. This parameter is supported starting from version 1.1. If the connections are closed by closing the socket or sending a COM_QUIT packet, this does seem to be a valid bug.

          People

            markus makela markus makela
            caisunny cai sunny
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.