(MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = mysqlĭon’t worry about the “non-compliant” message. (ServerService Thread Pool - 36) WFLYJCA0005: Deploying non-JDBC-compliant driver class (version 5.1) Add the following block after the “” entry for H2:Īfter you’ve added that, bounce your server and you should see the following messages in the log file to let you know that the driver was loaded: You should see a reference to the H2 JDBC driver here. WILDFLY_HOME/standalone/configuration/standalone.xml), and navigate to the “” section. Open the configuration file you’re using (e.g. Now, we need to tell the server about the new JDBC driver. Once that is done, you should have a folder that looks like this: Within this folder, you will need to copy the JDBC JAR file (Be sure to grab the latest driver!) and create a module.xml file with the following content: Once there, you’ll need to create another folder, called “main”.
#INSTALL MYSQL DRIVER WINDOWS INSTALL#
Let’s install the MySQL JDBC driver, so go ahead and create a com/mysql folder tree. These package folders correspond to the package of the extension.
If you navigate to this folder, you should see package folders. The advantage of installing it into Wildfly itself is that you can enforce a specific JDBC driver version for all of your deployed applications. However, if you are deploying an application to a clustered Wildfly, it could be better to deploy the JDBC driver along with your application.Īll of Wildfly’s “extensions” are located in WILDFLY_HOME/modules/system/layers/base. As long as you have access to Wildfly, installing the appropriate JDBC driver is fairly straightforward. Most likely, you have a different database such as Oracle, MS SQL, or MySQL. Out of the box, Wildfly only comes with an H2 JDBC driver.
0 kommentar(er)
