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
How to hide deleted users from the Users Section of the UI in RSA Via Lifecycle and Governance Number of Views Role membership rules configured in the RSA Identity Governance & Lifecycle's Role UI do not create rules when no checkbox… Number of Views In RSA Identity Governance & Lifecycle, a SQL exception error in the UI is encountered when saving Delay node on a Workflow Number of Views How to set jdbc URL in LDAP format to the "Common and Required Data Source Properties" in RSA IMG 6.8.1 Number of Views Menu bar on the top and footer section in the bottom on the UI are not visible after applying patch in RSA Governance & Li… Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
