Bug 1324772 - Editing of default deployment scanner's relative-to attribute can cause server crash
Summary: Editing of default deployment scanner's relative-to attribute can cause serve...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Server
Version: 6.4.7
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: Chao Wang
QA Contact: Pavel Slavicek
eap-docs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-07 09:13 UTC by Jan Kasik
Modified: 2016-09-05 08:35 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-09-05 08:35:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-3044 0 Critical Closed Editing of default deployment scanner's relative-to attribute can cause server crash 2016-09-05 08:35:23 UTC
Red Hat Issue Tracker WFCORE-1333 0 Critical Resolved Editing of default deployment scanner's relative-to attribute can cause server crash 2016-09-05 08:35:23 UTC

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
Note You need to log in before you can comment on or make changes to this bug.