Issue Details (XML | Word | Printable)

Key: CORE-3413
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vlad Khorsun
Reporter: Vlad Khorsun
Votes: 0
Watchers: 0
Operations

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

Improve diagnostics of internal trace errors

Created: 25/Mar/11 03:04 PM   Updated: 15/Jul/15 06:54 PM
Component/s: None
Affects Version/s: 2.5.0
Fix Version/s: 2.5.1, 3.0 Alpha 1

QA Status: Done successfully
Test Details:
Implemented for execution on Windows only.
1) This test uses async. calls of external routine (fbsvcmgr) with opening it in separate command window,
   see: subprocess.call('start /min cmd /c ...', shell=True).
2) It was encountered that launching trace session by FBSVCMGR requires 1-2 seconds to be finished,
   so this test intentionally uses delay (see calls `time.sleep()`).
3) Format of `database` section differ in 2.5 vs 3.0, so two separate sections have been created here for each FB version.
4) Correct work was checked on: WI-V2.5.5.26914 (SS, SC) and WI-V3.0.0.31940 (SS, SC and CS).
Test Specifics: Platform (Windows/Linux) specific


 Description  « Hide
In 2.5.0 all internal errors thrown by the trace plugin itself are logged at firebird.log. For example, when trace configuration contains regular expression in wrong syntax, wrong element, etc.

While this is OK for system audit it is not user-friendly (and even not necessary) for user trace sessions.

Improvement is to put such errors into trace output and not into firebird.log whenever possible.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.