MySQL Bugs: #62619: ClusterJ Crashes JVM

Bug #62619	ClusterJ Crashes JVM
Submitted:	4 Oct 2011 17:42	Modified:	23 Aug 2013 18:53
Reporter:	Ben Reeves	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster/J	Severity:	S3 (Non-critical)
Version:	7.21	OS:	MacOS (10.7)
Assigned to:		CPU Architecture:	Any

Description:
Hello,

I am trying to get ClusterJ up and running with mysql cluster 7.2.1 on OSX 10.7. As the distribution binaries don't contain clusterj.jar or libndbclient.dylib I compiled them separately. 

However the following Test app crashes the JVM:

import java.util.Properties;

import com.mysql.clusterj.ClusterJHelper;
import com.mysql.clusterj.Session;
import com.mysql.clusterj.SessionFactory;

public class Main {

    public static void main(String [] args)
	{
		Properties props = new Properties();
        
        props.put("com.mysql.clusterj.connectstring", "server1:1186");
        props.put("com.mysql.clusterj.database", "mydb");
	
        SessionFactory factory = ClusterJHelper.getSessionFactory(props);
        
        Session session = factory.getSession();
    }

}

com.mysql.clusterj.core.metadata.DomainTypeHandlerFactoryImpl <clinit>
INFO: Found 0 DomainTypeHandlerFactories
Invalid memory access of location 0x108 rip=0x101a11ff1
Segmentation fault: 11

Thanks

How to repeat:
Install Mysql cluster using mysql-cluster-gpl-7.2.1-osx10.6-x86_64.dmg

Download Mysql cluster source from mysql-cluster-gpl-7.2.1.tar.gz

cd ./mysql-cluster-gpl-7.2.1

cmake .

make clusterj.jar

make nbbclient_so

sudo cp ./storage/ndb/clusterj/clusterj-7.2.1.jar /usr/local/mysql/lib/

sudo cp ./storage/ndb/src/libndbclient.dylib  /usr/local/mysql/lib/

Run Java test app

java -classpath "/usr/local/mysql/lib/clusterj-7.2.1.jar:./" -Djava.library.path=/usr/local/mysql/lib Main

Thank you for the report.

There are Cluster packages for 10.7 now. Please try with them and inform us if problem still exists.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".