Repeated erroneous database driver error messages?

[Paul Suh]

I'm getting repeated database connection error messages in PWM.log:

2017-08-05T08:13:19Z, ERROR, db.JDBCDriverLoader,  unable to load database driver: ["AppPathFileLoader error: 5051 ERROR_DB_UNAVAILABLE (error registering JDBC database driver stored in configuration: com.mysql.jdbc.Driver)","Classpath error: 5051 ERROR_DB_UNAVAILABLE (java.lang.ClassNotFoundException error loading JDBC database driver from classpath: com.mysql.jdbc.Driver)"]

2017-08-05T08:13:19Z, WARN , db.DatabaseService, exception initializing database service: 5051 ERROR_DB_UNAVAILABLE ( unable to load database driver: ["AppPathFileLoader error: 5051 ERROR_DB_UNAVAILABLE (error registering JDBC database driver stored in configuration: com.mysql.jdbc.Driver)","Classpath error: 5051 ERROR_DB_UNAVAILABLE (java.lang.ClassNotFoundException error loading JDBC database driver from classpath: com.mysql.jdbc.Driver)"])

The problem is that I'm not using the MySQL driver. I'm using MariaDB and their JDBC driver, and the connection string is specified as "jdbc:mariadb://localhost:3306/pwm". The driver class (specified properly in the config) is "org.mariadb.jdbc.Driver". 

Windows Server 2016, brand new clean setup

Tomcat 8.5 latest build

PWM 1.8.0 - 2017-08-04 build. 

The server does seem to be talking to the MariaDB instance properly, it's just very strange that it keeps asking for com.mysql.jdbc.Driver, and it's polluting the log file every minute or so, making it difficult to troubleshoot other problems. 

Any ideas? 

--Paul

[Jason Rivard]

Did you copy a jdbc driver anywhere into the tomcat/ directory structure?  The only place you should put the file is uploaded in the config editor...

[Paul Suh]

Nope. The problem isn't the existence (or lack thereof) of the JDBC driver jar itself; it's that the app is requesting the mysql driver even when it's not configured to do so.