Hey Walter, My JAVA_HOME=C:\j2sdk1.4.2_12. So I don't have that problem. The application runs pretty well. It is only one data type that causes problems when loading the data. That really indicates a problem with the driver.
In resolving it, I just replaced the 3.1.x JDBC driver with the 3.0.x, restarted the server and was able to do the import of the uom_conversion table without any problems. Are you sure you're using the 3.1.x mySQL JDBC drivers ? Which version precisely are you using? I would like to report this problem to mysql.com. Thanks, John On 7/26/06, Walter Vaughan <[EMAIL PROTECTED]> wrote:
John Martin wrote: > Hi Si, > > Guess what, the problem is with the JDBC driver. I downgraded from > the 3.1.13 Connector/J 3.1 to the 3.0.17 as you mentioned and > everything worked fine. Uh, I am using that driver just fine... (In fact sitting here at OSCON just recreated your scenario to make sure I'm not speaking from foggy memory). What ALWAYS seemed to bite me when I started installing ofBiz is is having a path the the JDK with a space in a directory name in it. I'm using Sun's AppServer JDK on a XP laptop with 512M memory... C:\ofbiz>echo %JAVA_HOME% C:\Sun\AppServer\jdk and MySQL 5.0.22-community-nt edition "%JAVA_HOME%\bin\java" -Xms256M -Xmx512M -jar ofbiz.jar to get things going post hoc ergo prompter hoc YMMV -- Walter
