[
https://issues.jboss.org/browse/AS7-5043?page=com.atlassian.jira.plugin.s...
]
James Perkins edited comment on AS7-5043 at 10/15/12 8:38 PM:
--------------------------------------------------------------
This PR changes the filters to be a string based expression. This will allow for filters
to be expressed in a more fluid fashion.
<match pattern="(JBAS014101|JBAS011806)"/>
Example:
{code}
<filter
value="not(match("JBAS014101"),match("JBAS011806"))"/>
{code}
was (Author: jamezp):
This PR changes the filters to be a string based expression. This will allow for
filters to be expressed in a more fluid fashion.
<match pattern="(JBAS014101|JBAS011806)"/>
Example:
{code}
<filter
value="match("JBAS014101"),match("JBAS011806")"/>
{code}
Filtering of logging messages works incorrectly
-----------------------------------------------
Key: AS7-5043
URL:
https://issues.jboss.org/browse/AS7-5043
Project: Application Server 7
Issue Type: Bug
Components: Logging
Affects Versions: 7.1.1.Final
Reporter: Oleg Nitz
Assignee: James Perkins
In standalone.xml I'm trying to filter out wrong error messages:
<subsystem xmlns="urn:jboss:domain:logging:1.1">
<console-handler name="CONSOLE">
<filter>
<all>
<not><match pattern="JBAS014101: Failed to find SFSB
instance with session ID"/></not>
<not><match pattern="JBAS011806: Channel end notification
received, closing channel Channel ID"/></not>
</all>
</filter>
</console-handler>
But this doesn't work, and under debugger I see that the configuration got parsed as
"filter" => {"all" => {"not" => {"match"
=> "JBAS011806: Channel end notification received, closing channel Channel
ID"}}},
Looks like due to the use of maps for storing the parsing results the first
"not" filter got overwritten by the second "not" filter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira