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

Bug 1040067

Summary:	Seeding Startup time.
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Nick Cross <ncross>
Component:	Installer	Assignee:	Miroslav Sochurek <msochure>
Status:	CLOSED UPSTREAM	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	soa-p-jira
Target Milestone:	---
Target Release:	---
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:34:35 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Cross 2013-12-10 16:17:26 UTC

Currently the installer has to start up an entire server to do the s-ramp seeding. This means any other wars (e.g. dtgov) will be started as well due to the .dodeploy files (to trigger startup of exploded wars). 

If these other dodeploy files were moved/renamed/etc temporarily by the installer so only s-ramp was started for the seeding this might make the installation quicker.

Comment 2 Thomas Hauser 2014-01-07 21:35:27 UTC

Work for this feature has been completed and resides in a branch in the installer repo. It is not slated for inclusion in the FSW ga, however.

Comment 3 Thomas Hauser 2014-02-19 21:32:33 UTC

The feature branch has been merged into installer-commons.

Comment 7 Red Hat Bugzilla 2025-02-10 03:34:35 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.