Bug 996145
Summary: | Server fails to deploy RTGov, DTGov after installing S-RAMP into SOA 6 | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Stefan Bunciak <sbunciak> | ||||
Component: | Installer | Assignee: | Thomas Hauser <thauser> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.0.0 GA | CC: | atangrin, sbunciak, soa-p-jira, tkirby | ||||
Target Milestone: | ER3 | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 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: |
|
Description
Stefan Bunciak
2013-08-12 13:58:35 UTC
These errors occur while using the zips as well: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Download soa and sramp zips from http://dev138.mw.lab.eng.bos.redhat.com/candidate/soa-6.0.0.ER1/ 2. Unzip SOA on top of EAP 6.1.0.GA 3. Unzip S-RAMP onto this SOA unzip Actual results: * Extracts from server log after start-up: 10:29:45,974 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."overlord-rtgov.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."overlord-rtgov.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "overlord-rtgov.war" 10:29:47,620 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.module.service."deployment.switchyard-bpel-console.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.switchyard-bpel-console.war".main: JBAS018759: Failed to load module: deployment.switchyard-bpel-console.war:main 10:29:48,244 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.module.service."deployment.switchyard-bpel-console-server.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.switchyard-bpel-console-server.war".main: JBAS018759: Failed to load module: deployment.switchyard-bpel-console-server.war:main 10:30:01,546 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss Red Hat JBoss SRAMP 6.0.0.ER1-redhat-1 (AS 7.2.0.Final-redhat-8) started (with errors) in 26287ms - Started 529 of 738 services (124 services failed or missing dependencies, 83 services are passive or on-demand) Expected results: * Unzipping SOA onto EAP-6.1.0 and S-RAMP on top of that works correctly. In light of these errors, even with no additional configuration options selected in the installer (resultant directories are identical with installations done by simple unzipping), I would say it's a problem with the zips themselves. I confirm that this is reproducible also with the zips as well, as stated in https://bugzilla.redhat.com/show_bug.cgi?id=993272. That is quite expected behaviour since by extracting contents of the zips you are explicitly overwriting the server configuration, but the installer should cope with this and create a usable configuration for SOA6+S-RAMP+DTGov+RTGov. Without a spec of what this usable configuration should be, this is rather difficult to achieve. Who can provide this spec? I believe that such configuration spec should already exist, since there is a new installer comming to ER2: One Installer - does not include EAP 6.1 - allows users to install: - SOA/SwitchYard server - RTGov server -OR- RTGov client (mututally exclusive) - DTGov server (if this is selected, then S-RAMP is automatically installed) - S-RAMP This issue should be revisited when it's time for ER2. The configuration should all mesh successfully. Verified with S-RAMP 6.0.0.ER3. All 3 SOA Governance components are deployed. |