30 messages in com.mysql.lists.javaRe: connector mxj problems on linux
FromSent OnAttachments
Diego Zanga21 Apr 2006 10:14 
Eric Herman21 Apr 2006 12:11 
Eric Herman22 Apr 2006 10:48 
Eric Herman24 Apr 2006 14:38 
Eric Herman25 Apr 2006 12:49 
Andreas Schlicker27 Apr 2006 06:14 
Eric Herman27 Apr 2006 10:05 
Eric Herman27 Apr 2006 10:20 
Andreas Schlicker28 Apr 2006 01:07.java, .java
Andreas Schlicker28 Apr 2006 05:33 
Eric Herman28 Apr 2006 09:16 
Eric Herman28 Apr 2006 12:13 
Andreas Schlicker02 May 2006 03:56 
Eric Herman02 May 2006 15:31 
Andreas Schlicker03 May 2006 02:32 
Eric Herman03 May 2006 07:50 
Eric Herman03 May 2006 12:38 
Eric Herman03 May 2006 12:44 
Eric Herman04 May 2006 06:44 
Andreas Schlicker04 May 2006 08:03 
Eric Herman04 May 2006 09:25 
Andreas Schlicker04 May 2006 23:41.txt
Eric Herman05 May 2006 07:00 
Andreas Schlicker05 May 2006 07:51.txt
Andreas Schlicker05 May 2006 07:58 
Eric Herman08 May 2006 10:36 
Andreas Schlicker08 May 2006 23:20 
Eric Herman22 May 2006 07:07 
Andreas Schlicker26 May 2006 03:31 
Eric Herman26 May 2006 08:40 
Subject:Re: connector mxj problems on linux
From:Eric Herman (er@mysql.com)
Date:04/22/2006 10:48:21 AM
List:com.mysql.lists.java

Diego Zanga-

Thank you for your in-depth feedback and taking the time to dig into the source code. That's a rare pleasure. The "5.0" branch is under development at this time and some of the issues that you mention have been, or are planned to be, addressed in that branch.

You've encountered several things, so let me try to take them by category.

After long long long long long test, and awful debugging (wht's needed to rebuild the connector? junit and ????? )

Code dependencies: * For Connector/MXJ 5.0, Connector/J 5.0 is required. This is the beta version.

* JUnit is required to build the tests and can be downloaded from junit.org

* For JMX support, Either Java 1.5 or Java 1.4 with a JMX library.

* To build the sample JMX application, Sun's JMX's implementation is required. (In particular the "jmxtools.jar")

./npaMysql : is my base directory

It looks as though the first thing that was giving you trouble is the base directory. This has been addressed in the source tree of Connector/MXJ. However, in the mean time, when creating directories, rather than using the "." to specify working directory, using System.getProperty("user.dir") will avoid the errors that you are seeing.

String userDirStr = System.getProperty("user.dir"); File userDir = new File(userDirStr); File baseDir = new File(userDir, "npaMysql");

This should avoid the "datadir" and socket file creation, and PID file creation problems.

Alternatively use of java.io.File's canonical path would also work, I suspect.

In the next release of Connector/MXJ, this will not be an issue, and wherever wherever we converting between strings and files we will be using the file.getCanonicalPath().

Also, on the source tree of the Connector/MXJ 5.0 branch, if a socket file is not specified, the socket file in no longer placed in the "basedir", but in the "datadir".

3) MXJ jar needed to be fixed: it adds the parameter --no-default It DOESNT WORK on linux mysqld. So i've removed it in package com.mysql.management; MysqldResource.java

The "--no-defaults" option is added to avoid reading an existing "my.cnf" file from some other installation of MySQL on our system. I personal develop using linux and test under a couple of different linux configurations. This is the first report of an issue with "--no-defaults" ... if you could help me reproduce this problem I would like to get to the bottom of it. Next week I'll make sure I do some testing on SUSE 10.

Cheers, -- Eric

Are you MySQL certified? www.mysql.com/certification