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.

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

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.

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