Migrating using mysql database #2645

benprim · 1 decade ago

It looks like there's an issue while trying to migrate a server using mysql DB (from 5.0.7 to 5.1.6, I also tried 5.0.10 to check if it was because on the version gap.. but same results).

The bigining of the migration works fine but then I have this exception :

2014-01-09 14:11:19,001 INFO  - QuickBuild server stopped.
Exception in thread "main" java.lang.RuntimeException: java.sql.SQLException: No suitable driver found for jdbc:mysql://
localhost:3306/quickbuild
        at com.pmease.quickbuild.bootstrap.BootstrapUtils.wrapAsUnchecked(BootstrapUtils.java:56)
        at com.pmease.quickbuild.util.ExceptionUtils.wrapAsUnchecked(ExceptionUtils.java:82)
        at com.pmease.quickbuild.util.DbUtils.getConnection(DbUtils.java:101)
        at com.pmease.quickbuild.util.DbUtils.getDataVersion(DbUtils.java:129)
        at com.pmease.quickbuild.Quickbuild.getVersion(Quickbuild.java:871)
        at com.pmease.quickbuild.bootstrap.Migrate$3.execute(Migrate.java:288)
        at com.pmease.quickbuild.Quickbuild$3.run(Quickbuild.java:605)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/quickbuild
        at java.sql.DriverManager.getConnection(Unknown Source)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at com.pmease.quickbuild.util.DbUtils.getConnection(DbUtils.java:96)
        ... 5 more

The mysql jar libs are present in the new server plugins\com.pmease.quickbuild.libs directory ... but still I have the issue, tried to force the libs on CLASSPATH with no luck.

I manage to workaround using H2 as a temp solution for backup / restore...
But is this the way to do a migration (reverting to H2 table for migration) ? or is it a bug and QB should handle the migration by itself ?
Thanks

replies 6
views 2323
stars 0

robinshen ADMIN · 1 decade ago

H2 is not necessary as part of migration if you are using MySQL. Please make sure MySQL JDBC driver exists in "plugins\com.pmease.quickbuild.libs" of old QB instance (in your case 5.0.7) before running the migration.

benprim · 1 decade ago

Thanks Robin, then it looks like there's a bug in this process.
The plugin did exist in the old QB Instance (because... well I'm using Mysql as a database obviously <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /> )

robinshen ADMIN · 1 decade ago

I did the same test and it works fine. Can you please let me know below info?
1. OS type/version.
2. Java version.
3. MySQL server and jdbc driver version.

benprim · 1 decade ago

Thanks Robin.

Is there a specific way to do the migration ?
I mean what I just did is :
1) Get & extract the new version
2) go to new version's bin folder : migrate.bat PathToOldVersion

Right ?

Anyway the information you wanted are :
- Windows 7 64bit SP1
- Java 1.6.0_25
- Mysql 5.5 (jdbc mysql-connector-java-5.1.28)
Thanks again

robinshen ADMIN · 1 decade ago

This is the correct way to do the migration. I am using the same configuration but still can not reproduce? Any possibility that you can set up a WebEx or GotoMeeting session, so that I can take a look at this online?

benprim · 1 decade ago

I have to first make sure I can recreate the situation (as I mentionned before, I found a workaround using H2 as a temp DB).
thanks