|Applies To||RSA Product Set: RSA Identity Governance and Lifecycle |
RSA Product/Service Type: Enterprise Software
|Issue||When migrating an RSA Identity Governance and Lifecycle database from one version to another on a WebLogic platform, the migration output that is displayed in the User Interface (UI) may result in a java.lang.NullPointerException. The migration continues but no more output is logged to the UI.|
The aveksaServer.log contains the following:
01/11/2017 16:53:28.558 ERROR ([STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)') [MainManager]
The stdout.log contains the following messaging:
<Jan 11, 2017 5:24:53 PM CET> <Error> <WebLogicServer> <XXX-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'
|Cause||The process thread for the migration has exceeded the WebLogic Server Stuck Thread Max Time for inactivity.|
In this case the WebLogic Server Stuck Thread Max Time was set to 600 seconds, which is the default, and the process thread was inactive for longer than 600 seconds. Note the error occurred after 661 seconds of inactivity.
|Resolution|| The WebLogic Server Stuck Thread Max Time value can be modified. Use the WebLogic Console to change this value (base_domain > Environment > Servers > Admin Server > Configuration/Tuning).|
Please note you may want to set this value temporarily for a database migration and set it back to the normal value once the migration has completed. Normal is based on current site requirements. The WebLogic default value is 600.
|Workaround||Rather than reset the Stuck Thread Max Time value, you have two other options:|