AnsweredAssumed Answered

404 - Not Found after trying to restore customization files

Question asked by Philip Martinez on Mar 26, 2017

In Dev and QA we didn't run into this issue, but in Prod when we did customizeACM.sh -d the following occurred. Now I get 404 - Not Found. If I try to run customizeACM.sh again I get the same error when I do -d. The only difference between steps in Dev and QA and in Prod was that I turned on Maintenance Mode (on version 7.0.1 Patch 02, with RSA delivered Hotfix). 

 

Undeploying current ear...

 

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_116052_P02_HF03-2017-Mar-25-22.27.ear

 

aveksa_7.0.1_116052_P02_HF03-2017-Mar-25-22.27.ear archived

Outcomes