When initiating the openIDM startup while connected to the orientDB database, I would rarely (though often enough to blog about it). a startup issue with the following error response:
Caused by: com.orientechnologies.orient.core.exception.OSerializationException: Cannot load database's configuration. The database seems to be corrupted.
Never a good thing when you read that the read, The database seems to be corrupted
Anyhow, it seems this type of issue only related with OrientDB Databases. I've worked with the other noticable DBs out there and I've noticed this issue with various version of OpenIDM. Forgerock are often stating that OrientDB is not supported for production deployments so you shouldn't be running this in PROD anyway
The issue states that another process is already running and because of that, it cannot load the datbase configuration. It certainly worrying that within the openIDM stack trace there the words, The database seems to be corrupted.
Issue starting up OpenIDM
The script of the issue is below
Kill the java processes. Simply perform a ps -ef, locate the process ID that belongs to OpenIDM is running (you will see the path, 'openidm/bin/*' associated to it), then kill it. by running 'kill -9 1805' (assuming your process ID is 1805)
About the authorDaniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Received the JWT error
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
IDM ERROR - JDBC repository configured but datasource default was not found
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded