org.eclipse.persistence.exceptions.PersistenceUnitLoadingException
This error means you are running the wrong version of the Java JRE. Install Java version 8.x and try again.
java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7
This error means you are running the wrong version of the Java JDK. Install Java version 8.x and try again.
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper
This error means you are running the wrong version of the Java JDK. Install Java version 8.x and try again.
Could not initialize class org.codehaus.groovy.reflection.ReflectionCache
This error means you are running the wrong version of the Java JDK. Install Java version 8.x and try again.
java.lang.UnsatisfiedLinkError: no mtclijni64 in java.library.path
This error means that the c-treeDB Java driver could not find the client-side library:
On Windows the client-side library needs to be accessible in one of the folders of the path. Adjust the java.library.path systemProperty in the build.gradle file or adjust the path system variable or copy the client side library into a folder on the path.
On Linux there is an easy way to fix this. Issue the following command:
> export LD_LIBRARY_PATH=<path-to-client-side-library>
Note that it sometimes is enough to simply copy the client-side library into the current working directory.
javax.resource.ResourceException: c-tree logon error
This error means that the driver could not reach the server:
javax.resource.ResourceException: c-tree logon error
The most common cause of this runtime error is the FairCom Database Engine is not running on your machine. The most likely cause is that the c-tree evaluation license times out after 3 hours and shuts down the server. The solution is to restart the server; see Starting the FairCom Database Engine.
Make sure the server is running and not blocked by the firewall.
Make sure the connection information in persistence.xml is correct.
ResourceException: Can't connect to database
The following error means that the driver could reach the server but the database defined in persistence.xml does not exist.
To fix this issue, either create the database for example using the FairCom SQL Explorer or adjust the database name in persistence.xml to match an existing database.