Issue Details (XML | Word | Printable)

Key: CORE-3168
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Vlad Khorsun
Reporter: Thomas Steinmaurer
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

exclude_filter doesn't work for <services></section> section of the Trace facility

Created: 07/Oct/10 03:58 PM   Updated: Sunday 12:06 PM
Component/s: Engine
Affects Version/s: 2.5.0
Fix Version/s: 2.5.1, 3.0 Alpha 1

QA Status: Done with caveats
Test Details:
Test implemented for WINDOWS platform only, checked on WI-V2.5.5.26916 (SS, SC) and WI-V3.0.0.31948 (SS, SC, CS).


 Description  « Hide
I have the following trace config:

<services>
   enabled true
   log_services true
   exclude_filter "List Trace Sessions"
</services>

Although I've set the exclude filter (also tried without enclosed double quotes), I do get entries like that:


2010-10-07T11:39:12.3090 (1856:0148D0A4) START_SERVICE
service_mgr, (Service 012B6A94, SYSDBA, TCPv4:192.168.142.1,
G:\APPLICAT\FBTraceManager\exe\debug\FBTraceManager.exe:5132)
"List Trace Sessions"
-TRUSTED_SVC SYSDBA -LIST

2010-10-07T11:39:17.3250 (1856:0148D0A4) START_SERVICE
service_mgr, (Service 012B6A94, SYSDBA, TCPv4:192.168.142.1,
G:\APPLICAT\FBTraceManager\exe\debug\FBTraceManager.exe:5132)
"List Trace Sessions"
-TRUSTED_SVC SYSDBA -LIST

I've also tried the following exclude_filter which should dismiss all trace service events:

exclude_filter %Trace%

Running the following SIMILAR TO based query:

select 1 from rdb$database where 'Start Trace Session' similar to '%Trace%'

shows, that the result of the WHERE condition is true, thus fulfills the regular expression, so there is something wrong when evaluating the exclude_filter in the trace facility.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Vlad Khorsun added a comment - 26/Jul/15 09:08 AM
Pavel,
you excluded "List Trace Sessions" event, but your command line start *another* service - "Start Trace Session".
Trace output in your sample shows "Start Trace Session" service, not (filtered out by you) "List Trace Sessions".
Do you see the difference ?

Pavel Zotov added a comment - 26/Jul/15 12:03 PM
>> So, I can`t understand: does this bug still exists (and is this behavour a *bug* per se ?)
> you excluded "List Trace Sessions" event, but your command line start *another* service - "Start Trace Session".

Vlad, thanks. I was inattentive.