Link: Added: This issue is incorporated by JBQA-5357

This issue seems to be fixed in the latest AS 7.1 release.

However feedback for errors on the console was very poor. I made silly errors while creating the handler and I got no feedback on the console. The server log had these errors. Heiko, I'm leaving this issue open to hear your comments about user feedback, feel free to close this issue after that, maybe create a new one to fix the user feedback issue.

16:45:52,278 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.logging.handler.file-test: org.jboss.msc.service.StartException in service jboss.logging.handler.file-test: java.io.FileNotFoundException: /home/rrajasek/Desktop (No such file or directory)
16:46:50,015 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.logging.handler.test-file-logger: org.jboss.msc.service.StartException in service jboss.logging.handler.test-file-logger: java.io.FileNotFoundException: /home/rajesh (Is a directory)

Stan, can you comment on this? I assume it's lack of error reporting of the management layer.

This is not critical for ER1 as the issue is only with error reporting. Moving to ER4

Rajesh, I'm not seeing this.  Can you provide specific steps to recreate?

Nikoleta, can you try to reproduce the issue (error reporting) on the ER4 build when it becomes availble? 

Results with ER4 build:

Verified that original issue about not allowing to change log file location/name is fixed.

However, the error reporting still seems poor. 

After changing File Path or File Relative To of existing handler to incorrect value, it is not saved and 
the original value remains there. I would expect some warning about incorrect path and information about 
changing it in console and server log but nothing happens.

Errors occur if the incorrect value is typed while adding new handler. These errors are logged in server log 
but there is no feedback from console. The handler is just not created.

13:08:22,109 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.logging.handler.test-file-log: org.jboss.msc.service.StartException in service jboss.logging.handler.test-file-log: java.io.FileNotFoundException: /home/nziakova (Is a directory)
	at org.jboss.as.logging.handlers.file.FileHandlerService.start(FileHandlerService.java:70)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
	at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: java.io.FileNotFoundException: /home/nziakova (Is a directory)
	at java.io.FileOutputStream.open(Native Method) [rt.jar:1.6.0_26]
	at java.io.FileOutputStream.<init>(FileOutputStream.java:194) [rt.jar:1.6.0_26]
	at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:152) [jboss-logmanager-1.2.2.GA-redhat-1.jar:1.2.2.GA-redhat-1]
	at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:183) [jboss-logmanager-1.2.2.GA-redhat-1.jar:1.2.2.GA-redhat-1]
	at org.jboss.as.logging.handlers.file.FileHandlerService.start(FileHandlerService.java:68)
	... 5 more

Steps to reproduce:
1. log in to Web Management Interface
2. add new File Handler with File Path which does not exist or is a directory
3. handler is not created but console says nothing, error is logged in server log

Closing this jira as the original issue is fixed for ER4.
Created new issue for error reporting.

Link: Added: This issue relates to JBPAPP-8626

Docs QE Status: Removed: NEW