Article Number
000038350
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
Patching RSA Identity Governance & Lifecycle fails with:
Starting application server to import patched ear ....at Thu Jan 16 17:16:22 EST 2020
Deploying patched ear file...
Error deploying the ear file
The patch log file located in $
AVEKSA_HOME/<patch-directory-name>/logs shows more information on this error:
Deploying new customized ear... this may take a while...
Exception encountered while deploying Aveksa.ear
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" =>
{"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE" =>
"org.jboss.msc.service.StartException in service jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE:
WFLYSRV0153: Failed to process phase CONFIGURE_MODULE of deployment \"aveksa.ear\"
Caused by: org.jboss.msc.service.DuplicateServiceException:
Service jboss.module.spec.service.\"deployment.jboss-logging-3.3\".main is already registered"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"aveksa.ear\".CONFIGURE_MODULE"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}
Aveksa.ear deployment failed after 1 minutes, 31.494 seconds
Updating CURRENTLY_DEPLOYED_ARCHIVE to aveksa_7.1.1_161195_P04-2020-Jan-16-17.19.ear
aveksa_7.1.1_161195_P04-2020-Jan-16-17.19.ear archived
An error occured in the customizeACM command : error code 5
Error deploying the ear file
Step failed! See /home/oracle/Aveksa_7.1.1_P04/logs/7.1.1_P04_2020-01-16-1644.log for more information.
if you encounter this error running
customizeACM.sh, please see related RSA Knowledge Base Article
000038632 -- customizeACM.sh fails with 'Undeploy failed:' error in RSA Identity Governance & Lifecycle for resolution.
Cause
The deployed aveksa ear file has a name other than aveksa.ear.
By default, the RSA Identity Governance & Lifecycle installation, patch/upgrade and customizeACM.sh processes automatically deploy the ear file with the name aveksa.ear and expect the name of the ear file to be aveksa.ear when they go to undeploy the ear.
In cases where the ear file has been deployed manually, it is possible to deploy the ear file with a name other than aveksa.ear. In this case future patching, upgrading and customization of the ear file will fail.
Resolution
Manually undeploy the current ear file and re-install the patch.
- Login as the oracle user
- Determine the name of the currently deployed ear file:
$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="deployment-info"
You will see output similar to the following:
NAME RUNTIME-NAME PERSISTENT ENABLED STATUS
aveksaWFArchitect.ear aveksaWFArchitect.ear true true OK
<name other than aveksa.ear> <name other than aveksa.ear> true true OK
This is the reason for the patch failure. The name should be aveksa.ear.
- Undeploy the ear file. (Standalone)
$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy <name of deployed aveksa ear file>"
- Undeploy the ear file. (Clustered)
$AVEKSA_HOME/wildfly/bin/jboss-cli.sh -c --controller="127.0.0.1:9999" --command="undeploy <name of deployed aveksa ear file> --server-groups=img-server-group"
- Login as the root user and re-install the patch.
su root
cd <patch-directory>
./patch.sh
To avoid the problem in the future:
If you are deploying the ear file manually and not through patching, upgrading or
customizeACM.sh, ensure that the ear file is deployed as
aveksa.ear by following the instructions in RSA Knowledge Base Article
000038351 -- How to manually deploy an aveksa ear file in RSA Identity Governance & Lifecycle.
