Bug 1138085
| Summary: | Fail to deploy dashbuilder.war due to dependency name mismatch. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ryan Zhang <rzhang> | ||||
| Component: | BAM | Assignee: | David Gutierrez <dgutierr> | ||||
| Status: | CLOSED EOL | QA Contact: | Gui Jospin <gjospin> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 6.0.0 | CC: | kverlaen, mbaluch, rrajasek, rzhang | ||||
| Target Milestone: | ER3 | ||||||
| Target Release: | 6.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-03-27 20:08:58 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
I see the http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.1.0-DR2/jboss-bpms-6.1.0.redhat-1-deployable-eap6.x.zip contains the jboss-all.xml file with the right dependency inside. So I'm wondering why it fails. The jboss-all.xml file does not exist in community nor in the product branch. So I guess it's added during the productization build. Aside from figuring out the causes of the error above, one thing we could do is to add the jboss-all.xml to the product branding branch so that is always available for productization to build. Created attachment 936388 [details]
jboss-all-xml.patch
The solution applied consists in adding the jboss-all.xml to the jbpm-dashboard productized build. The following command: [drooljbpm/jbpm-dashboard] mvn clean install -Dfull -Dproductized ... it adds the https://github.com/droolsjbpm/jbpm-dashboard/blob/master/jbpm-dashboard-modules/jbpm-dashboard-redhat/src/main/webapp/META-INF/jboss-all.xml descriptor to the EAP6.3, AS7 & Widlfly 8 WAR distributions. Thanks to this, patches or any other post-processing of the generated WAR file to make the jbpm-dashboard depend on business central is no longer needed. Github commits (master) ---------------------------- https://github.com/droolsjbpm/jbpm-dashboard/commit/d2390cd0ca13295907e6ba03c98beac98e290c2d https://github.com/droolsjbpm/kie-wb-distributions/commit/ebe7606c716d759728a43042c1f81d5992da3824 Github commits (6.2.x) ---------------------------- https://github.com/droolsjbpm/jbpm-dashboard/commit/dfe589420b43f7e92269bcf98daa743149e913f1 https://github.com/droolsjbpm/kie-wb-distributions/commit/23b65d077347841357d3bbafee8044585f10c776 From QE point of view the BPM Suite 6.1.0 build ER3 deploys correctly. I guess it's up to productization to check the build settings has been fixed correctly. Ryan, can you please verify this BZ? Yes, this issue is fixed. I have clean the workaround patch. Thanks Jan for confirmation. |
Description of problem: Dashbuilder.war failed to deploy in BPMS 6.1.0 DR2. See error log at [1]. The reason is that: dashbuilder.war/META-INF/jboss-all.xml defines: <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0"> <dependency name="kie-eap-distributions-bpms-webapp-6.2.0.Beta1-redhat-1-kie-wb.war" /> </jboss-deployment-dependencies> However in product, kie*.war is renamed to business-central.war jbpm-dashbuilder is renamed to dashbuilder.war So it can't find the correct dependency war. [1]: 11:24:58,745 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (ServerService Thread Pool -- 88) errai bus started. 11:24:58,848 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "dashbuilder.war" (runtime-name : "dashbuilder.war") 11:24:58,849 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "business-central.war" (runtime-name : "business-central.war") 11:24:58,850 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.deployment.unit."kie-eap-distributions-bpms-webapp-6.2.0.Beta1-redhat-1-kie-wb.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."dashbuilder.war".PARSE] 11:24:58,951 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 11:24:58,952 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 11:24:58,953 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss BPM Suite 6.1.0.Alpha (AS 7.4.0.Final-redhat-19) started (with errors) in 18964ms - Started 815 of 853 services (1 services failed or missing dependencies, 70 services are lazy, passive or on-demand) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: