Bug 1203101

Summary: [GSS] (6.4.z) logViewer can not show expression file name
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: jooho lee <jlee>
Component: LoggingAssignee: Ivo Studensky <istudens>
Status: CLOSED WONTFIX QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: brian.stansberry, harshada, hpehl, istudens, jkudrnac, lgao, pjelinek, thofman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-24 13:46:22 UTC 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:

Description jooho lee 2015-03-18 06:18:48 UTC
Description of problem:
In log subsystem, nested expression can be used for path.
~~
"path" => {
                        "type" => STRING,
                        "description" => "The filesystem path.",
                        "expressions-allowed" => true,
                        "nillable" => false,
                        "min-length" => 1L,
                        "max-length" => 2147483647L
                    }
~~

so if I use following log configuration :
~~~
<periodic-rotating-file-handler name="FILE" autoflush="true">
                <formatter>
                    <named-formatter name="PATTERN"/>
                </formatter>
				<file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
~~~

server log name will be HOST_NAME.log and there is no problems to write.

However, it is not displated in Admin console Log Viewer menu.

Version-Release number of selected component (if applicable):
6.4.beta

How reproducible:
change path in <periodic-rotating-file-handler> file element to ${jboss.server.name}.log

Then see admin console menu.
Steps to Reproduce:
1.
2.
3.

Actual results:
empty

Expected results:
~.log file should be shown.

Additional info:

Comment 1 Lin Gao 2015-03-25 10:31:29 UTC
The problem is that the string: "${jboss.server.name}.log" is passed to server for filtering, and the server does not expand the expression before filtering the file names.

Thus this should be related to component: logging.