000038449 - Invalid Request error accessing workflows after patching/upgrading RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Feb 10, 2020Last modified by RSA Customer Support Employee on Mar 16, 2020
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000038449
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.x
 
Issue
After upgrading or patching RSA Identity Governance & Lifecycle, the application is running but workflows are inaccessible. In the RSA Identity Governance & Lifecycle user interface, navigate to Requests > Workflows > any tab > {workflow name} or Requests > Requests > {request name} > Processing Workflow.
 


Invalid Request

 

User-added image



The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log):
 

2020-01-16 10:14:18,216 [Worker_alertq#Role#jdbc/avdb_6] ERROR com.workpoint.queue.work.AlertQWorker -
Exception caught during alert evaluation.
Alert 'DependencyCheckToCompleteWorkItem', AlertID=76:WPDS, JobID=4760:WPDS, ProcessRef='WF_FF_17',
WorkItem=55970:WPDS:1, FIFO=19787464 (offset=836646ms)
Exception was: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space


You allocate more memory to java, finish the upgrade and restart RSA Identity Governance & Lifecycle but the problem remains.

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform.
 
CauseThe significant error in this case is:
 
java.lang.OutOfMemoryError: Java heap space


Running out of memory can cause unpredictable behavior. In this case, running out of space caused the workflows to be inaccessible.
 
ResolutionThe resolution to this issue depends on the symptom(s) encountered when running out of Java heap space. See the Workraround section in this RSA Knowledge Base Article for possible solutions.
 
WorkaroundIn this case redeploying the workflow architect ear file and restarting RSA Identity Governance & Lifecycle solved the issue. 
  1. Determine if the workflow architect ear file is currently deployed:


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deployment-info"


If the RSA Identity Governance & Lifecycle workflow architect ear file is deployed, it needs to be undeployed. If the ear file is already undeployed, skip to step 4 if standalone and step 5 if clustered.


  1. Undeploy the workflow architect ear file (Standalone)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy aveksaWFArchitect.ear"


  1. Undeploy the workflow architect ear file (Cluster)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy aveksaWFArchitect.ear
--server-groups=img-server-group"


  1. Deploy the workflow ear file (Standalone).


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999"
--command="deploy $AVEKSA_HOME/Aveksa_<patch-directory>/aveksaWFArchitect.ear"


  1. Deploy the workflow ear file (Cluster)


$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999"
--command="deploy $AVEKSA_HOME/Aveksa_<patch-directory>/aveksaWFArchitect.ear --server-groups=img-server-group"


  1. Restart RSA Identity Governance & Lifecycle


acm restart

If this does not resolve your issue, please contact RSA Identity Governance & Lifecycle Support for further assistance.
 

Attachments

    Outcomes