Documentation Home
MySQL NDB Cluster API Developer Guide
Download this Manual ClusterJException

ClusterJException is the base for all ClusterJ exceptions. Applications can catch ClusterJException to be notified of all ClusterJ reported issues.

  • User exceptions are caused by user error, for example providing a connect string that refers to an unavailable host or port.

  • Datastore exceptions report conditions that result from datastore operations after bootstrapping. For example, duplicate keys on insert, or record does not exist on delete. com.mysql.clusterj.ClusterJDatastoreException

  • Internal exceptions report conditions that are caused by errors in implementation. These exceptions should be reported as bugs. com.mysql.clusterj.ClusterJFatalInternalException

Exceptions are in three general categories: User exceptions, Datastore exceptions, and Internal exceptions. Synopsis
 public class ClusterJException extends, RuntimeException {
// Public Constructors  public ClusterJException(String message);
  public ClusterJException(String message,
                           Throwable t);

  public ClusterJException(Throwable t);
// Public Methods  public synchronized void printStackTrace(PrintStream s);

Direct known subclasses: com.mysql.clusterj.ClusterJDatastoreException , com.mysql.clusterj.ClusterJFatalException , com.mysql.clusterj.ClusterJUserException

Methods inherited from java.lang.Throwable: addSuppressed , fillInStackTrace , getCause , getLocalizedMessage , getMessage , getStackTrace , getSuppressed , initCause , printStackTrace , setStackTrace , toString

Methods inherited from java.lang.Object: equals , getClass , hashCode , notify , notifyAll , wait

User Comments
User comments in this section are, as the name implies, provided by MySQL users. The MySQL documentation team is not responsible for, nor do they endorse, any of the information provided here.
Sign Up Login You must be logged in to post a comment.