000034978 - Deploying a new customized RSA Identity Governance and Lifecycle ear fails with JBAS014653: Composite operation failed and JBAS014671: Failed services

Document created by RSA Customer Support Employee on Mar 29, 2017Last modified by RSA Customer Support Employee on May 30, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034978
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.1
 
IssueAfter installing a 7.0.1 patch and running 'customizeACM.sh -d', deploying the new ear fails with:
 
Deploying new customized ear... this may take a while... 
{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" =>
{"jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.EventMDBean.START" => "org.jboss.msc.service.StartException in service
jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.EventMDBean.START: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException:
IJ000263: WorkManager is shutting down
Caused by: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
Caused by: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down","jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.UtilityMDBean.START"
=> "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.UtilityMDBean.START: java.lang.RuntimeException:
javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
Caused by: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
Caused by: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down","jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.ServerAutomatedActivityMDBean.START"
=> "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"aveksa.ear\".\"wpServer.jar\".component.ServerAutomatedActivityMDBean.START: java.lang.RuntimeException:
javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
Caused by: java.lang.RuntimeException: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down
Caused by: javax.resource.spi.work.WorkRejectedException: IJ000263: WorkManager is shutting down"},"JBAS014771: Services with missing/unavailable dependencies"
=> ["jboss.deployment.subunit.\"aveksa.ear\".\"wpConsole.war\".INSTALL is missing [jboss.deployment.subunit.\"aveksa.ear\".\"wpQMonitor.war\".deploymentCompleteService]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.ORB is missing
[jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.deployment.unit.\"aveksa.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"aveksa.ear\".\"wpQMonitor.war\".deploymentCompleteService,
jboss.deployment.subunit.\"aveksa.ear\".\"wpClientServletLite.war\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"server.jar\".deploymentCompleteService,
jboss.deployment.subunit.\"aveksa.ear\".\"wpConsole.war\".deploymentCompleteService]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.InstanceName is missing
[jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.InAppClientContainer is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.deployment.subunit.\"aveksa.ear\".\"wpClientServletLite.war\".INSTALL is missing
[jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".deploymentCompleteService]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.ValidatorFactory is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.deployment.subunit.\"aveksa.ear\".\"wpQMonitor.war\".INSTALL is missing
[jboss.deployment.subunit.\"aveksa.ear\".\"wpClientServletLite.war\".deploymentCompleteService]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.HandleDelegate is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".INSTALL is missing
[jboss.deployment.subunit.\"aveksa.ear\".\"server.jar\".deploymentCompleteService]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.Validator is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]"]}}}
Aveksa.ear successfully redeployed
Updating CURRENTLY_DEPLOYED_ARCHIVE to aveksa_7.0.1_<new ear>.ear
aveksa_7.0.1_<old ear>.ear archived

CauseThis is a timing issue where it is taking more time than expected/allowed to start the WildFly application server.
Resolution
  1. Navigate to /home/oracle/deploy/wildfly-conf/groovy/com/aveksa/wildfly.
  2. Make backups of the Datasources.groovy, Messaging.groovy and Util.groovy files, as shown below:
cd /home/oracle/deploy/wildfly-conf/groovy/com/aveksa/wildfly 
cp -p Datasources.groovy Datasources.groovy.orig
cp -p Messaging.groovy Messaging.groovy.orig
cp -p Util.groovy Util.groovy.orig

  1. Open the Datasources.groovy, Messaging.groovy and Util.groovy files in a text editor.
  2. There will be one occurrence in each file of a setting:
Thread.sleep(10000)

  1. Change the 10000 to 60000. This will make the install script allow a full minute for the WildFly application to start.  
  2. After making this change, rerun customizeACM.sh -d.
NotesRelated article: KB 000033056 - RSA Identity Governance &amp; Lifecycle 7.0.0 installation fails with the following error:&#160; JBAS014653: Composite operation failed and was rolled back

Attachments

    Outcomes