Details

    • Steps to Reproduce:
      Hide
      1. Set up a MariaDB server using MariaDB repository and using version '10.3.4' or '10.3' which will default to the latest version:
        cat << EOF >> /etc/yum.repos.d/MariaDB.repo
        [mariadb]
        name = MariaDB
        baseurl = http://yum.mariadb.org/10.3/centos7-amd64
        gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
        gpgcheck=1
        EOF
        yum makecache fast && yum install mariadb-server socat jemalloc MySQL-python -y;
        
      2. Configure Keycloak to use MariaDB driver and the datasource
      3. Start fresh keycloak instance and it hangs on 'Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml' for some time
      4. After some time, Keycloak will report that there's a SQL error (as defined in previous attachment)
      5. Any further restarts will result in failure (please see keycloak_restart_failures.txt)
      Show
      Set up a MariaDB server using MariaDB repository and using version '10.3.4' or '10.3' which will default to the latest version: cat << EOF >> /etc/yum.repos.d/MariaDB.repo [mariadb] name = MariaDB baseurl = http://yum.mariadb.org/10.3/centos7-amd64 gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1 EOF yum makecache fast && yum install mariadb-server socat jemalloc MySQL-python -y; Configure Keycloak to use MariaDB driver and the datasource Start fresh keycloak instance and it hangs on 'Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml' for some time After some time, Keycloak will report that there's a SQL error (as defined in previous attachment) Any further restarts will result in failure (please see keycloak_restart_failures.txt)
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      As of MariaDB 10.3.4 (and presumeably later), I'm unable to launch new Keycloak instances. This is due to the following error (from JBoss), please see mariadb_10.3.4_error.log (unable to add attachments at the moment).

      I assume it's due to the fact of this change: https://github.com/MariaDB/server/commit/01a8bad897

      Which can be found in MariaDB 10.3.4 changelog (https://mariadb.com/kb/en/library/mariadb-1034-changelog/, SQL: allow PERIOD as identifier fixes #33).

      A workaround for this issue: use MariaDB 10.3.3 or lower.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  hmlnarik Hynek Mlnařík
                  Reporter:
                  operations-2 IS4U Support
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  13 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: