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

Bug 1324772

Summary:	Editing of default deployment scanner's relative-to attribute can cause server crash
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jan Kasik <jkasik>
Component:	Server	Assignee:	Chao Wang <chaowan>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Slavicek <pslavice>
Severity:	high	Docs Contact:	eap-docs <eap-docs>
Priority:	unspecified
Version:	6.4.7	CC:	chaowan, jason.greene
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-05 08:35:15 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:

Description Jan Kasik 2016-04-07 09:13:20 UTC

Description of problem: Setting value of relative-to attribute of default deployment scanner on standalone server to a path which does not exists in file system causes server crash.


Version-Release number of selected component (if applicable): 6.4.7

Steps to Reproduce:

1. Start server in standalone mode
2. Change value of relative-to attribute to non-existing value. /subsystem=deployment-scanner/scanner=default:write-attribute(name=relative-to, value=foobar)
3. :reload
4. Server is down and have to be started with corrected configuration. Cannot be fixed using CLI.


Actual results: Server should be available after reload.


Expected results: Server crashes with an exception and it is not possible to start it without correcting the xml configuration first.

Comment 3 JBoss JIRA Server 2016-08-23 11:38:32 UTC

Jiri Pallich <jpallich> updated the status of jira JBEAP-3044 to Closed