Bug 915670
| Summary: | Console allows creation of File Handler with invalid path without rising any error message | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jakub Cechacek <jcechace> |
| Component: | Logging | Assignee: | James Perkins <jperkins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikoleta Hlavickova <nziakova> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | brian.stansberry, jkudrnac, kkhan, pkremens |
| Target Milestone: | DR7 | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 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: | |||
This is logging subsystem problem. Assigning to brian for further delegation Need an upstream JIRA. Verified with EAP 6.4.0.DR7. |
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)