Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1138656

Summary: S-RAMP is not started successfully because of dependecies problems
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Jiri Sedlacek <jsedlace>
Component: Build ProcessAssignee: Julian Coleman <jcoleman>
Status: CLOSED UPSTREAM QA Contact: Matej Melko <mmelko>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: oskutka, soa-p-jira
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:42:56 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:
Description Flags
fuse.log none

Description Jiri Sedlacek 2014-09-05 11:36:52 UTC 
Created attachment 934752 [details]
fuse.log

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1136314, there are missing dependencies. If these missing imports are added, it helps little bit, but s-ramp is still not started successfully, fuse.log after running

features:install switchyard
features:install s-ramp

is attached.


I'm not sure that even if fixed dependencies it will start smoothly, because in comparison with s-ramp installed from community zip, there are missing many files in DR2 and there is no additional realm configured in jetty.xml (does it need to be there?).
Comment 5 Red Hat Bugzilla 2025-02-10 03:42:56 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.