Skip to main content

Unable to find the driver com.mysql.jdbc.Driver. Register the driver in the Databases tab

This happened when you tried to create an entity from a database. I am currently using Wildfly 8.1.0, and MySQL 5.1.30 on NetBeans 8.0.

To resolve this issue, open the standalone-full.xml of JBOSS.
Under the datasources > drivers > driver, make sure the driver name is the same as the datasource > driver.

For example, make sure the text highlighted in the following code block is the same:


<subsystem xmlns="urn:jboss:domain:datasources:2.0">
    <datasources>
        <datasource jta="false" jndi-name="java:jboss/mysql" pool-name="mysql" enabled="true" use-ccm="false">
            <connection-url>jdbc:mysql://localhost:3306/client</connection-url>
            <driver-class>com.mysql.jdbc.Driver</driver-class>
            <driver>mysql</driver>
        </datasource>
        <drivers>
            <driver name="mysql" module="com.mysql">
                <driver-class>com.mysql.jdbc.Driver</driver-class>
            </driver>
        </drivers>
    </datasources>
</subsystem>

Labels:

Comments

Post a Comment

Popular posts from this blog

Fix HTTP error code 513 on Wildfly

The Mysterious Case of TIME_WAIT and IDLE Connections Have you ever encountered a network issue where your server is consistently showing a high number of connections in the TIME_WAIT and IDLE states? This phenomenon can be frustrating, especially when it indicates that the connections are not being closed properly by the server or client. In our investigation, we found that the culprit behind this issue was an HTTP error code 513 being sent to clients from servers. This error code indicates that the server is overloaded and cannot handle more requests. Furthermore, the client was logging a socket close event, which meant it was terminating the connection prematurely. To replicate this issue, we used JMeter and found that the max concurrent connection limit was reached, resulting in an HTTP error code 513. The allowed queue was also full, contributing to the problem. So, what are the consequences of this issue? Performance degradation and resource wastage on both servers and clients ca...
Post a Comment
Read more

Wildfly EJB Remote Client Exceptions.......

Below are exceptions and the solutions I applied while developing a remote client enterprise application. To start with, enable debug for your application server to see the detail and good luck troubleshooting. Exceptions : Starting with  java.lang.ClassNotFoundException: org.hibernate.collection.internal.Persistent......... Solution : I fixed the exception be adding hibernate Entity Manager Dependencies. Exception: Error javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial Solution : Add JBOSS-CLIENT Dependencies to your project Exception : IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling Solution : Confirm that your EJB module have been deployed. Exception : org.jboss.naming.remote.client.initialcontextfactory wildfly     javax.naming.NamingException: WFLYNAM0027: F...
Post a Comment
Read more

No EJB found with interface of type with Jboss annotation @Management in JavaEE6

“JBoss-specific @Management is not supported with Java EE6-specified @Singleton,” as quoted here: https://developer.jboss.org/thread/164844 . A workaround will be to annotate with @Singleton and @Startup. Also, you could expose your bean through JMX with the snippet below: MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();          ObjectName name = new ObjectName("com.example:type=Hello");          Hello mbean = new Hello();          mbs.registerMBean(mbean, name); Read More  
Post a Comment
Read more