- Product: RSA Governance and Lifecycle
- Version: 8.0.x (e.g., 8.0.0 P08 / P08 HF02)
- Component: WorkPoint Workflow Engine
- Platform: IBM WebSphere Application Server (WAS 9.0) — Clustered or Standalone environments
After upgrading or applying a patch to RSA Governance and Lifecycle on IBM WebSphere Application Server, all newly submitted Change Requests (CRs) stall at the initial action node after the "Start" node and fail to advance into the Approval or Fulfillment phases. Requests accumulate in an Open state with 1 error badges.
Observable Symptoms:
- Workflows display the message:
Workflow flagged as stalled based on stall detection settings. - In the UI under Admin > Workflow > Monitoring, the Activity panel is empty, the Queues section displays no items, and all three System Status Indicators show RED.
wpqmonitor.logandWorkPoint.logare frozen — no new polling entries are recorded.- Thread dumps from the System Operations Node (SON) show that WorkPoint queue worker threads are missing entirely:
Worker_alertq#,Worker_actionq#,Worker_eventq#,Worker_jobq#. - An unexpanded variable path appears on the filesystem:
.../BaseMCWAS90_profile/${workpoint.log.dir.custom}/wpqmonitor.log
Key Error Lines in aveksaServer.log:
The following errors appear during application startup on the System Operations Node:
ERROR [com.workpoint.server.monitor.ManagementServices] An error was encountered when attempting to start the Workpoint Queue Monitors
javax.management.InstanceNotFoundException: WPServer:name=WpQMonitors
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1107) ~[?:1.8.0]
Also the below errors are seen when trying to submit more change requests:
ERROR [com.workpoint.server.WpLoginHandler] Login failed for user AveskaAdmin
javax.security.auth.login.LoginException: Only the super admin account is supported
at com.aveksa.server.workflow.authentication.WpAveksaLoginModule.authenticate(WpAveksaLoginModule.java:256) ~[server-workflow-integration.jar:?]
The WebSphere environment variable workpoint.log.dir.custom is undefined or missing in the WebSphere Application Server configuration profile.
Without this variable, the path is treated literally as ${workpoint.log.dir.custom}, which prevents WorkPoint logging from initializing during server startup. As a result, the WorkPoint Queue Monitors MBean (WPServer:name=WpQMonitors) fails to register with JMX, and the queue worker threads never start. This commonly happens when the variable is not preserved or re-created during an upgrade or patch deployment to RSA Governance and Lifecycle deployed on WebSphere.
ℹ️ NOTE: The steps below resolve the issue on existing 8.0.x environments using IBM WebSphere (WAS).
Step 1: Define the workpoint.log.dir.custom Variable in WebSphere
Follow the instructions in the RSA Governance and Lifecycle 8.0 Installation Guide, Appendix B: Troubleshooting, under the section "Configuring WorkPoint Logs for WebSphere" (page 200) to define the workpoint.log.dir.custom variable in your WebSphere Application Server configuration profile.
Step 2: Stop the WebSphere Cluster
Stop the entire WebSphere cluster, including all General Nodes and the System Operations Node (SON).
Step 3: Start the System Operations Node (SON)
Perform a clean restart of the System Operations Node (SON) first. Wait until the SON is fully available and accessible in the web browser before proceeding.
Step 4: Start All General Nodes
Once the SON is confirmed available, start all General Nodes so that inter-node SIBus/JMS messaging and clustering are fully operational.
Step 5: Monitor wpqmonitor.log on Startup
Confirm that the WorkPoint Queue Monitors have started successfully by monitoring the log:
tail -f /<path_to_logs>/wpqmonitor.log
You should see entries similar to:
INFO com.workpoint.queue.WpQMonitors - PRODUCT = Workpoint ...
INFO com.workpoint.queue.WpQMonitors - Loaded queue monitor configuration from ...
Step 6: Verify Workflow Engine Status in the UI
- Log into the RSA Governance & Lifecycle UI as an administrator.
- Navigate to Admin > Workflow > Monitoring.
- Verify that the Queues section displays active counts and queue monitor workers are running.
- Navigate to Admin > System > Server Nodes.
- Confirm all nodes report healthy and log streaming is functional.
✅ TIP: Submit a test Change Request to confirm that workflows now advance past the Start node into the Approval and Fulfillment phases as expected.
There is no workaround for this issue. Active WorkPoint queue monitor workers are required to advance workflow jobs. Apply the full resolution above to restore workflow processing.
- Permanent Fix: A permanent fix is targeted for RSA Governance and Lifecycle future release / patch, which will validate required WebSphere properties during patch synchronization.
- Thread Dump Verification: To confirm this issue before applying the fix, take a thread dump from the running SON node (
javacore.*.txt) and check for the presence of WorkPoint queue worker threads:Worker_alertq#,Worker_actionq#,Worker_eventq#,Worker_jobq#. If all four are missing, this article applies. - Unexpanded Variable Path: A quick way to identify this issue on the filesystem is to look for the literal unexpanded string
${workpoint.log.dir.custom}in your log paths (e.g.,.../BaseMCWAS90_profile/${workpoint.log.dir.custom}/wpqmonitor.log). If the variable has not resolved to an actual directory, the property is missing. - Related — Similar Workflow Stall Scenario: ACM-143827 — Covers workflows stalling at SQL/data set nodes where Change Requests are blocked from reaching the Approval phase. If workflows stall at nodes other than the initial Start node, the issue is different than the one in this article and this article does not apply.
- Related — Installation Guide Reference: RSA Governance and Lifecycle 8.0 Installation Guide — Contains the full procedure for configuring WorkPoint logs for WebSphere in Appendix B: Troubleshooting.
Related Articles
multiple services crashing on multiple servers and dat files be duplicated on storage locations 27Number of Views Unification fails at Step 7/11 with 'ORA-54017: UPDATE operation disallowed on virtual columns' in RSA Identity Governance… 91Number of Views upgrade adds geoip_SHORTRUN_1.dat 18Number of Views Certificate is issued with certdn value from CMP request rather than the one in ss.dat when CMP Server is configured with … 26Number of Views Unable to login to ACM using Authentication Source with Remote Active Directory type - RSA Via L & G 270Number of Views