WebLogic database migration UI output displays a java.lang.NullPointerException in RSA Identity Governance and Lifecycle
Originally Published: 2017-01-11
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
Platform: WebLogic
Issue
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]
java.lang.NullPointerException
at com.aveksa.migration.jdbctool.CheckDatabase.followOutput(CheckDatabase.java:2589)
at com.aveksa.migration.jdbctool.CheckDatabase.handleRequest(CheckDatabase.java:2342)
at com.aveksa.gui.core.ACMManager.checkHandleRequest(ACMManager.java:62)
at com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:142)
at com.aveksa.gui.core.MainManager.doGet(MainManager.java:128)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:280)
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)'
has been busy for "661" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@4f1ceb6c[GET /aveksa/main]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
java.lang.Thread.sleep(Native Method)
com.aveksa.migration.jdbctool.CheckDatabase.followOutput(CheckDatabase.java:2597)
com.aveksa.migration.jdbctool.CheckDatabase.handleRequest(CheckDatabase.java:2342)
com.aveksa.gui.core.ACMManager.checkHandleRequest(ACMManager.java:62)
com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:142)
com.aveksa.gui.core.MainManager.doGet(MainManager.java:128)
javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
javax.servlet.http.HttpServlet.service(HttpServlet.java:844)
Cause
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
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
- Refresh the browser window when the null pointer exception occurs. This causes the thread to activate and continue logging information.
- Alternatively, tail the migrate.log to monitor migration progress.
Related Articles
AFX Connectors remain in a Not Deployed state and templates show (Migration Required) in RSA Identity Governance & Lifecycle Number of Views WorkPoint.log and heap dumps are written to the Linux root directory ( / ) on WebSphere and WebLogic implementations of RS… Number of Views After an upgrade and migration, the 'Is Terminated' user attribute is not updated after unification in RSA Identity Govern… Number of Views RSA Identity Governance and Lifecycle MigrationReports.zip fails to install Migration Reports with ORA-04063: package body… Number of Views RSA Authentication Manager 8.6 Hardware Appliance Getting Started Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
