Bug 900152 (JBPAPP6-1483) - Poor feedback for errors in Web Management Interface
Summary: Poor feedback for errors in Web Management Interface
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: JBPAPP6-1483
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: TBD EAP 6
Assignee: Nikoleta Hlavickova
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-04 11:36 UTC by Nikoleta Hlavickova
Modified: 2014-06-28 12:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-26 10:10:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 899501 0 high CLOSED Web Management Interface does not allow to change log file location/name 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 899820 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 915670 0 unspecified CLOSED Console allows creation of File Handler with invalid path without rising any error message 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPAPP6-1483 0 Major Closed Poor feedback for errors in Web Management Interface 2014-08-13 11:20:06 UTC

Internal Links: 899501 899820 915670

Description Nikoleta Hlavickova 2012-04-04 11:36:13 UTC
Steps to Reproduce: 1. log in to Web Management Interface
2. switch to Logging section
3. add new File Handler with File Path which does not exist or is a directory
4. handler is not created but console says nothing, error is logged in server log
project_key: JBPAPP6

After changing File Path or File Relative To of existing log 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

Comment 1 Nikoleta Hlavickova 2012-04-04 11:37:56 UTC
Link: Added: This issue is related to JBPAPP-7151


Comment 2 Rajesh Rajasekaran 2012-04-09 16:55:56 UTC
Link: Added: This issue relates to JBPAPP-8094


Comment 3 Stan Silvert 2012-04-20 22:35:06 UTC
You do get an error in the upper righthand corner.  It goes away after a few seconds and then you can retrieve it by clicking on "Messages".

Please look at this again and assign back to me if you still see a problem.

Note that I'm looking at the very latest version of console in master so you might need to wait until Heiko puts a new version into AS.

Comment 4 Rajesh Rajasekaran 2012-09-20 18:38:07 UTC
Labels: Added: eap601-qe-triage


Comment 5 Anne-Louise Tangring 2012-10-08 15:08:35 UTC
Not approved for EAP 6.0.1. If this should be reconsidered, please add the label: eap601-qe-triage

Comment 6 Anne-Louise Tangring 2012-10-08 15:08:35 UTC
Labels: Removed: eap601-qe-triage 


Comment 7 Anne-Louise Tangring 2012-11-13 21:00:28 UTC
Docs QE Status: Removed: NEW 


Comment 8 Jakub Cechacek 2013-02-26 10:10:48 UTC
Closing this issue as console's behavior has changed a bit since the bug was reported. However new BugZilla was created - see 915670


Note You need to log in before you can comment on or make changes to this bug.