Error when Attempting a NoSQL Connection using Cluster/J (Doc ID 1918416.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Cluster - Version 7.2 and later
Information in this document applies to any platform.

Symptoms

On : 7.2 version, Cluster/J

When attempting to connect using the NoSQL method,
the following error occurs.

ERROR
-----------------------
Exception in thread "main" com.mysql.clusterj.ClusterJFatalUserException: Error getting connection to cluster with properties
{com.mysql.clusterj.connect.verbose=1, com.mysql.clusterj.jdbc.password=XXXXXXX, com.mysql.clusterj.connect.delay=5, com.mysql.clusterj.connectstring=mysqlserver.example.com:3306, com.mysql.clusterj.jdbc.username=appuser, com.mysql.clusterj.database=mydb_repository}
:
Caused by com.mysql.clusterj.ClusterJDatastoreException:Datastore exception on connectString 'mysqlserver.example.com:3306' nodeId 0; Return code: -1 error code: 1,006 message: Illegal reply from server: .


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup Cluster and Cluster/J capabilities
2. Set Cluster/J details to connect to the MySQL port of 3306
3. Attempt to connect

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot connect via NoSQL interface.

Changes

 This change is from the standard MySQL protocol to the NoSQL protocol via ndbapi.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms