AnsweredAssumed Answered

./customizeACM.sh -d giving error

Question asked by Rajkiran Paul on Nov 4, 2019
Latest reply on Nov 5, 2019 by Ian Staines

I am getting below error when i am trying to run below command.

 

 

Verifying that wildfly is running

Nov 04, 2019 12:14:24 PM java_util_logging_Logger$info call
INFO: checkIfWildflyRunning - Checking server status
Nov 04, 2019 12:14:24 PM java_util_logging_Logger$info call
INFO: Connecting to check connection
WARN: can't find jboss-cli.xml. Using default configuration values.
Nov 04, 2019 12:14:25 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.0.Final
Nov 04, 2019 12:14:25 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.0.Final
Nov 04, 2019 12:14:25 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 4.0.6.Final
Nov 04, 2019 12:14:25 PM java_util_logging_Logger$info call
INFO: checkIfWildflyRunning - Found server in running state
Nov 04, 2019 12:14:25 PM java_util_logging_Logger$info call
INFO: Terminate session

Wildfly is running

Repackaging the aveksa.war and aveksa.ear

Archive name is: aveksa_7.0.0_93958_P05-2019-Nov-04-12.14.ear

Creating aveksa.ear file for deployment
[zip] Building zip: /tmp/customizeACM/aveksa.war
[zip] Building zip: /tmp/customizeACM/aveksa.ear
[copy] Copying 1 file to /home/oracle/archive

Undeploying current ear...
Undeploy failed: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014807: Management resource '[(\"deployment\" => \"aveksa.ear\")]' not found"}}

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.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","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.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"},"JBAS014771: Services with missing/unavailable dependencies" => ["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.Validator is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","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.InAppClientContainer is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","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.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.ValidatorFactory is missing [jboss.naming.context.java.comp.aveksa.server.SubscriberMDB]","jboss.naming.context.java.comp.aveksa.server.SubscriberMDB.ORB 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.deployment.unit.\"aveksa.ear\".deploymentCompleteService is missing [jboss.deployment.subunit.\"aveksa.ear\".\"server.jar\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"wpQMonitor.war\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"wpConsole.war\".deploymentCompleteService, jboss.deployment.subunit.\"aveksa.ear\".\"wpClientServletLite.war\".deploymentCompleteService]"]}}}

Aveksa.ear successfully redeployed

Updating CURRENTLY_DEPLOYED_ARCHIVE to aveksa_7.0.0_93958_P05-2019-Nov-04-12.14.ear

aveksa_7.0.0_93958_P05-2019-Nov-04-12.14.ear archived

 

 

Somebody, please help to resolve this issue.

Outcomes