wood burning stoves 2.0*
The moose likes JBoss/WildFly and the fly likes ClassNotFoundException Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "ClassNotFoundException" Watch "ClassNotFoundException" New topic
Author

ClassNotFoundException

Bjorn Andersson
Greenhorn

Joined: Nov 19, 2003
Posts: 1
Hi!
I have a problem when starting my Jboss server!
Anyone that have a clue?
I get the following fault when I start the server:
09:59:10,647 ERROR [EntityContainer] Starting failed
org.jboss.deployment.DeploymentException: Error while fixing table name; - nested throwable: (org.jboss.util.NestedSQLException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver); - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver)))
I have the following environment:
jboss-3.2.1_tomcat-4.1.24
Mysql 4.0.16
mysql-connector-java-3.0.9-stable-bin
(situated in dir: %JBOSS_DIST%\lib\)
mysql-ds.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!--================================================ -->
<!-- Datasource config for MySQL using 2.0.11 driver-->
<!--================================================ -->

<datasources>
<local-tx-datasource>
<jndi-name>MySQLDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/employee</connection-url>
<driver-class>org.gjt.mm.mysql.Driver</driver-class>
<user-name>bjornan</user-name>
<password>bjornan</password>
</local-tx-datasource>
</datasources>
norman richards
Author
Ranch Hand

Joined: Jul 21, 2003
Posts: 367
Originally posted by Bjorn Andersson Bjorn Andersson:
Hi!
I have the following environment:
jboss-3.2.1_tomcat-4.1.24
Mysql 4.0.16
mysql-connector-java-3.0.9-stable-bin
(situated in dir: %JBOSS_DIST%\lib\)


Do you have the actual jar file containing the mysql jdbc driver in your lib directory? You can also test by placing the jdbc jar file directly in the deploy directory. You really wouldn't want to run like that, but it will let you more easily test your configuration because you can add/remove it and get the fast deploy behaviour...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: ClassNotFoundException