javax.jdo.JDOFatalUserException

Invalid datastore driver class "mysql-connector-java-3.1.11-bin" : maybe you havent specified the JDBC driver JAR in your CLASSPATH, or the name of the class is incorrect.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web98

  • via romaframework by erandika
    , 1 year ago
    Invalid datastore driver class "mysql-connector-java-3.1.11-bin" : maybe you havent specified the JDBC driver JAR in your CLASSPATH, or the name of the class is incorrect.
  • The specified driver class "null" is neither a java.sql.Driver nor a javax.sql.DataSource. Please specify a valid driver in the javax.jdo.option.ConnectionDriverName property.
  • via Oracle Community by 3004, 1 year ago
    The specified driver class "null" is neither a java.sql.Driver nor a javax.sql.DataSource. Please specify a valid driver in the javax.jdo.option.ConnectionDriverName property.
  • Stack trace

    • javax.jdo.JDOFatalUserException: Invalid datastore driver class "mysql-connector-java-3.1.11-bin" : maybe you havent specified the JDBC driver JAR in your CLASSPATH, or the name of the class is incorrect. at org.jpox.datasource.DriverManagerDataSource.<init>(DriverManagerDataSource.java:85) at org.jpox.AbstractPersistenceManagerFactory.freezeConfiguration(AbstractPersistenceManagerFactory.java:257) at org.jpox.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:534) at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:478) at org.romaframework.aspect.persistence.jdo.JDOPersistenceAspect.aspectStartup(JDOPersistenceAspect.java:185) at org.romaframework.core.aspect.AspectManager.startup(AspectManager.java:46) at org.romaframework.core.config.RomaApplicationContext.init(RomaApplicationContext.java:41) at org.romaframework.core.config.RomaApplicationContext.setup(RomaApplicationContext.java:101) at org.romaframework.aspect.view.echo2.Echo2StartupServlet.init(Echo2StartupServlet.java:45) at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:383) at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:329) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:405) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) at org.mortbay.http.HttpServer.service(HttpServer.java:909) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:982) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.