Summary

      The latest MySQL driver is now 8.0.11, which is the default when going to

      Our documentation links to that page.
      It does not work with Confluence 6.8.1.

      Using this driver causes some AO_ tables to not be successfully created during the database setup stage.

      Environment

      • MySQL 5.7
      • MySQL Connector 8.0.11

      Steps to Reproduce

      1. Download the latest MySQL 8.0.x Driver from
      2. As per the Confluence MySQL instructions, copy the driver to <confuence-install>/confluence/WEB-INF/lib
      3. Start a fresh install of Confluence

      Expected Results

      Installation completes without error.

      Actual Results

      The below exception is thrown in the atlassian-confluence.log file:

      2018-04-21 15:29:21,920 ERROR [http-nio-8090-exec-3] [atlassian.confluence.event.ConfluenceEventDispatcher] run There was an exception thrown trying to dispatch event [com.atlassian.plugin.event.events.PluginFrameworkStartedEvent@5de08ea6
      ] from the invoker [com.atlassian.confluence.event.ConfluenceListenerHandlersConfiguration$TimingListenerHandler$1$1@75222ad5]
       -- referer: http://localhost:8090/setup/setupdbtype-start.action | url: /setup/setuppaths.action | traceId: 00d2c7ac5f3ff7d9 | userName: anonymous | action: setuppaths
      java.lang.RuntimeException: bundle [com.atlassian.plugins.atlassian-whitelist-core-plugin]. Listener: com.atlassian.plugins.whitelist.core.applinks.ApplicationLinkChangeListener event: com.atlassian.plugin.event.events.PluginFrameworkStar
      tedEvent
      ...
      Caused by: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.plugins.atlassian-whitelist-core-plugin]
      ...
      Caused by: java.lang.RuntimeException: Could not read fields for table AO_21D670_WHITELIST_RULES
      ...
      Caused by: java.sql.SQLSyntaxErrorException: Table 'confluence681.AO_21D670_WHITELIST_RULES' doesn't exist
      

      In total the tables that are not created are

      • AO_21D670_WHITELIST_RULES
      • AO_26DB7F_ENTITIES_TO_ROOMS
      • AO_2F1435_HEALTH_CHECK_STATUS
      • AO_5FB9D7_AOHIP_CHAT_LINK
      • AO_6384AB_DISCOVERED
      • AO_92296B_AORECENTLY_VIEWED
      • AO_9412A1_AONOTIFICATION
      • AO_BAF3AA_AOINLINE_TASK

      Notes

      For now, our documentation should be updated to link to the 5.1 driver.

      Workaround

      Continue to use the 5.1.x driver from

            [CONFSERVER-55399] MySQL Java Driver 8.0.11 does not work with Confluence

            gross0r added a comment -

            I tested the 8 driver like you tell us on your homepage for confluence.

            With mySql8 it didn't work - can't be established a connection through the driver.

            Then i redownloaded the newest 5.1 driver (5.1.49) and ...

            ... nothing works.

            Everytime Unable to acquire JDBC Connection

            Is there anyone who has the same problem ?

            gross0r added a comment - I tested the 8 driver like you tell us on your homepage for confluence. With mySql8 it didn't work - can't be established a connection through the driver. Then i redownloaded the newest 5.1 driver (5.1.49) and ... ... nothing works. Everytime Unable to acquire JDBC Connection Is there anyone who has the same problem ?

            I ran into this issue when I upgraded, I think I had the new driver. The error continued to show in my logs even after I removed the incorrect version and added the old version. I was able to resolve it by re-running the installer and choosing "upgrade" even though it was the same revision of confluence.

            FreeSoftwareServers added a comment - I ran into this issue when I upgraded, I think I had the new driver. The error continued to show in my logs even after I removed the incorrect version and added the old version. I was able to resolve it by re-running the installer and choosing "upgrade" even though it was the same revision of confluence.

            Hi Chris,

            Sorry to hear you've had a difficult time migrating to Cloud. We don't currently support using any 8.x drivers for MySQL. Confluence is tested with the 5.1.42 driver, and this is the version we recommend (which can be used with either of the currently supported versions of MySQL)

            You can find information on supported drivers on this page https://confluence.atlassian.com/display/DOC/Database+JDBC+Drivers

            If you continue to have problems with the migration assistant, our support team will be happy to help.

            Rachel Robins added a comment - Hi Chris, Sorry to hear you've had a difficult time migrating to Cloud. We don't currently support using any 8.x drivers for MySQL. Confluence is tested with the 5.1.42 driver, and this is the version we recommend (which can be used with either of the currently supported versions of MySQL) You can find information on supported drivers on this page https://confluence.atlassian.com/display/DOC/Database+JDBC+Drivers If you continue to have problems with the migration assistant, our support team will be happy to help.

            Chris Barrett added a comment - - edited

            I had this issue after using the Migration Assistant and running into a problem that recommended upgrading to the latest MySQL driver 8.0.16, Migration Assistant 2.0.3, Confluence 6.15.2. Rolled back to 5.1.47 to get my site working again. Unable to run Migration Assistant due to a bug in 5.x ...

             

             

            https://confluence.atlassian.com/confkb/database-connection-issues-due-to-queries-leading-to-data-modification-are-not-allowed-361726204.html

            Chris Barrett added a comment - - edited I had this issue after using the Migration Assistant and running into a problem that recommended upgrading to the latest MySQL driver 8.0.16, Migration Assistant 2.0.3, Confluence 6.15.2. Rolled back to 5.1.47 to get my site working again. Unable to run Migration Assistant due to a bug in 5.x ...     https://confluence.atlassian.com/confkb/database-connection-issues-due-to-queries-leading-to-data-modification-are-not-allowed-361726204.html

            I have updated our documentation to make it clearer that you should use the 5.1.x driver, and updated the link to point to the 5.1.x download page, rather than latest.

            Rachel Robins added a comment - I have updated our documentation to make it clearer that you should use the 5.1.x driver, and updated the link to point to the 5.1.x download page, rather than latest.

            Hi @James

            Same issue on our side.

            Just had to setup a new environment, used 8.0.11 as current driver and ran into several AO_* issues.
            Overall looked Ok, but that failed.

            Reverting to 5.1.46 now and rechecking.

            Damn damn damn. What changed?

             

            Florian Meyer added a comment - Hi @James Same issue on our side. Just had to setup a new environment, used 8.0.11 as current driver and ran into several AO_* issues. Overall looked Ok, but that failed. Reverting to 5.1.46 now and rechecking. Damn damn damn. What changed?  

              rrobins Rachel Robins
              jrichards@atlassian.com James Richards
              Affected customers:
              0 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: