Hi Devs, I had same issue and i think there is more to it than just the jdbc driver being old. This is what happened with me: I moved Derby out of process and let it run as NetworkServer. I changed repository.xml to use SimplesDbPersristenceManager. I expected JR to start using NetworkServer but it was still using derby in embedded mode. Problem was, getConnection() method eats the SQLException and starts using embedded derby driver silently. In my case, it was failing because username for Derby running in NetworkServer mode was not provided. Thanks and regards Tushar Yufeng Li <[EMAIL PROTECTED]> wrote: Looks like it is because my jdbc driver is too old. I upgraded the driver from mysql-connector-java 3.1 to 5.X and it works fine now.
yufeng --- Yufeng Li wrote: > Hi; > > In my window environment, I configured mysql as the > persistence store (SimpleDbPersistenceManager) and > it > works fine. > > However, after I try to deploy it to Linux > environment > (mysql is also on linux). Everytime, when I tried to > start the app, it complains ...VERSION_NODE, > ..._VERSION_PROP, etc tables exists. If I recreated > the database, it would work fine till I restart the > app. Any clue on how to configure it not to recreate > the tables every time? > > Thanks. > --------------------------------- Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit.
