AnsweredAssumed Answered

Deployment failed: accessmanagement.war, backoffice.war, etc AAoP 7.3

Question asked by Rodolfo Rodriguez Zavala on Oct 2, 2018
Latest reply on Oct 9, 2018 by Jasmine Zakir Hussain

Hello, I'm doing a clean standalone setup in a QA environment  for AAoP 7.3 (before update to AAoP 7.4 P4) in a Red Hat Server 7.3, with Jboss 6.4 and Java 1.8, with a SQL 2012 DB server, I already finished to pre and post setup according at the official documentation, but anytime when I want to deploy some war files, always fail:

 

Deployment failed: accessmanagement.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.web.deployment.default-host./accessmanagement" : "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./accessmanagement: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\n Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}, "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}

 

Deployment failed: backoffice.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.web.deployment.default-host./backoffice" : "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./backoffice: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\n Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}, "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}

 

Deployment failed: casemanagement.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.web.deployment.default-host./casemanagement" : "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./casemanagement: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\n Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}, "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}

 

Deployment failed: reportviewer.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.web.deployment.default-host./reportviewer" : "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./reportviewer: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\n Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}, "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}

 

Deployment failed: wscredentialmanager.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.web.deployment.default-host./wscredentialmanager" : "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./wscredentialmanager: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\n Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}, "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}

 

 

For the next war files, the deployment is successfull
wm_resource_adapter.war
AdaptiveAuthentication.war
AdaptiveAuthenticationAdmin.war
aggDeviceToken.war
BrowserEventAnalyzer.war

 

Any ideas??, 

 

Best Regards!

Attachments

Outcomes