ClusterJException is the base for all ClusterJ exceptions. Applications can catch ClusterJException to be notified of all ClusterJ reported issues.
Exceptions are in three general categories: User exceptions, Datastore exceptions, and Internal exceptions.
-
User exceptions are caused by user error, for example providing a connect string that refers to an unavailable host or port.
If a user exception is detected during bootstrapping (acquiring a SessionFactory), it is thrown as a fatal exception.
com.mysql.clusterj.ClusterJFatalUserExceptionIf an exception is detected during initialization of a persistent interface, for example annotating a column that doesn't exist in the mapped table, it is reported as a user exception.
com.mysql.clusterj.ClusterJUserException
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.ClusterJDatastoreExceptionInternal exceptions report conditions that are caused by errors in implementation. These exceptions should be reported as bugs.
com.mysql.clusterj.ClusterJFatalInternalException
public class com.mysql.clusterj.ClusterJException extends java.lang.RuntimeException {
// Public Constructorspublic ClusterJException(java.lang.String message);public ClusterJException(java.lang.String message,
java.lang.Throwable t);public ClusterJException(java.lang.Throwable t);
// Public Methodspublic synchronized void printStackTrace(java.io.PrintStream s);
}
Direct known subclasses:
com.mysql.clusterj.ClusterJDatastoreException
, com.mysql.clusterj.ClusterJFatalException
, com.mysql.clusterj.ClusterJUserException
Methods inherited from
java.lang.Throwable:
fillInStackTrace
, getCause
, getLocalizedMessage
, getMessage
, getStackTrace
, initCause
, printStackTrace
, setStackTrace
, toString
Methods inherited from
java.lang.Object:
equals
, getClass
, hashCode
, notify
, notifyAll
, wait
