Bug 915670 - Console allows creation of File Handler with invalid path without rising any error message
Summary: Console allows creation of File Handler with invalid path without rising any ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR7
: EAP 6.4.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 10:02 UTC by Jakub Cechacek
Modified: 2019-08-19 12:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 900152 0 high CLOSED Poor feedback for errors in Web Management Interface 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFCORE-171 0 Major Open File handlers should not allow already existing directories as a file name 2014-10-15 15:55:48 UTC

Internal Links: 900152

Description Jakub Cechacek 2013-02-26 10:02:50 UTC
It is possible to create a new File Handler with invalid log file (e.g. using a directory path as log file or location without writing permissions) without console showing some error message (action is considered successful). 
  
Steps to reproduce

1. Navigate Profile - Core - Logging - Handler - File 
2. Add new File handler using this input

relative to: jboss.server.log.dir
file path: /foo/bar

3. save (Handler was successfully created)
4. Add another handler using this input

relative to: jboss.server.log.dir
file: /foo

5. save 
6. console shows that handler was successfully created, even though exception have been logged on server side.  


Expected behavior: In second case handler shouldn't be created as obviously path ${jboss.server.log.dir}/foo is a directory (created when first logger was saved)

Comment 1 Heiko Braun 2013-02-26 10:09:01 UTC
This is logging subsystem problem. Assigning to brian for further delegation

Comment 2 James Perkins 2013-03-08 00:55:56 UTC
Need an upstream JIRA.

Comment 5 Nikoleta Hlavickova 2014-10-30 08:19:24 UTC
Verified with EAP 6.4.0.DR7.


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