File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes JDBC and the fly likes Issues upgrading Mysql 4.1 to Mysql 5.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Issues upgrading Mysql 4.1 to Mysql 5.1" Watch "Issues upgrading Mysql 4.1 to Mysql 5.1" New topic
Author

Issues upgrading Mysql 4.1 to Mysql 5.1

Shashidhar Dakuri
Greenhorn

Joined: Mar 20, 2009
Posts: 1
i am not sure if i am posting in the right forum, if i am not please excuse me

i have an xml file which defines two actions, for two different states



i have a java class which parses this xml and updates the database.
in the first step, the field has to be updated from "reviewing_ofc" to "converting" and in the second step, i read this value of "converting" and then modify it to "awaiting_download".

we have used MySql 4.1 for a very long time now and we never had any issues with it. but now since i have upgraded to MySQL 5.1, i started having this problem.

on my developer machine, earlier i used to get an error no transition "notify_records" found for action "reviewing_ofc". so essentially before the write action is performed, the read action is taking place. i thought this might be some connector issues, so i searched for all the traces of the previous connector mysql-connector 3.0.8 , and when i removed all the traces of it. the application was working fine, i had no issues for a long time. when i work with the same application on different machines. on some machines , i got the same error, on some i never got that error even though i never changed anything or even removed the traces of previous connectors. now that was weird. there was this particular build machine, on which i had deployed the application and there were no issues for a long time. but one find day suddenly, i got that error, and that broke the application.
1) on some machines, i never got that error.
2) on some machines, i always get that error.
3) on some machines, it happens randomly

all the machines have same configurations.

windows xp, jboss 4.0.5, jdk 1.4, mysql 5.1 with connector 5.0.8.

the solution that i have right now is, if i go back to mysql 4.1, everything works like a charm, like nothing ever happened before. i would really appreciate it , if someone can help me with this issue. or else all the time i spent on upgrading from mysql 4.1 to 5.1 will be wasted.

Regards,
Shashi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Issues upgrading Mysql 4.1 to Mysql 5.1