OIM 11g Recon Error - Caused By: java.lang.InstantiationError java.lang.VirtualMachineError

While integrating OIM 11g with the ICF connector resource for reconciliation, I would often get the following error, javax.servlet.ServletException: java.lang.InstantiationError: java.lang.VirtualMachineError after a couple of attempts:
August 9, 2015
OIM-11gAdapters

This error was in conjunction with another blog, ADF_FACES-60098:Faces lifecycle receives unhandled exceptions java.lang.VirtualMachineError. Whereby the error publishing could be resolved by clearing out the JOB_HISTORY table with the rows related to your scheduled task.

https://technicalconfessions.com/images/postimages/postimages/_406_2_ADF_FACES60096 Server Exception during PPR 1.png

I did however notice that this issue became more frequent. Furthermore, the reconciliation data that was not coming in as expected. As mentioned within the blog, The solution was somewhat temporary though the root cause was unknown until later on. As a check, the server had sufficient memory available as well as the java managed server being allocated JVM max of 8GB as well as the Max Heap Size being 2GB. The full Stack from the nohup.out logs are as follows: The following error within the GUI would be, java.land.VirtualMachineError ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with : ADF_FACES-60096:Server Exception during PPR #1


SOLUTION

The stack trace within the server logs didn't provide much information on the issue. The information which identified the root cause resided within the BLOB within the JOB_HISTORY table. When searched for the scheduled task within the JOB_HISTORY table, you'll probably see at least one of the jobs with a status=6.

Within the same record, there's an 'ERROR_DATA' column, which contain the BLOB. When you double-click this, ensure you then click, 'view as text' of which you're likely to see the error. Alternatively, you ran run the following SQL script to see the blob in the text format: What would looks like corrupted text,

you will find something that resembles english text. Regarding my issue, you can see the error for failing to instantiation error is because the Virtual Memory was, out of space in CodeCache for Adapter.

https://technicalconfessions.com/images/postimages/postimages/_406_6_Error within OIM JOB_HISTORY BLOB.png

This issue was resolved by allocating memory to the cache. The argument entered within the managed server started was -XX:ReservedCodeCacheSize=256m. Once that was allocated, the issue was resolved

Example
DEFAULT_MEM_ARGS="${DEFAULT_MEM_ARGS} -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=256m" PORT_MEM_ARGS="${PORT_MEM_ARGS} -XX:PermSize=256m -XX:MaxPermSize=512m -XX:ReservedCodeCacheSize=256m"

About the author

Daniel 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

Comments

Other Posts

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
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.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
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.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
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
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...
E_WARNING Error in file posts.php at line 464: fopen(http://www.technicalconfessions.com/images/postimages/postIcons/pp444.png): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error

TomcatJava-8PKICAS

June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...