Bug 1203101 - [GSS] (6.4.z) logViewer can not show expression file name
Summary: [GSS] (6.4.z) logViewer can not show expression file name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ivo Studensky
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-18 06:18 UTC by jooho lee
Modified: 2019-10-10 09:41 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-24 13:46:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-637 0 Optional Open /subsystem=logging/log-file resource cannot cope with an expression in the path 2016-10-20 14:25:45 UTC

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.


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