21.04.2016 12:00, Thomas Steinmaurer wrote: >> Have you had time to look at it?
Looking now, but seems you already on the way ;) >> Unfortunately this now also has happened in a production environment at >> a customer site. >> >> We did quite some testing in the trace area at Firebird 3 Alpha stage >> and I can't remember any troubles there (in hope my memory serves me >> well). So I will move back from Final to Alpha2 in a test environment >> and see what happens. > > Seems to be something introduced with RC1 or possibly some sort of > incompatibility with (Delphi) client components using the Trace API? > > Beta2 (Firebird-3.0.0.31896-0_Win32_Beta2) seems to be fine and does not show > the symptom of fully utilizing a single core. RC1 have this bug fixed: http://tracker.firebirdsql.org/browse/CORE-4897 probably it is related. As you already found that fbtracemgr is OK, i guess something is not fully correct (or stepped on some another issue) at FB Trace Manager. Could you show how do you work with trace service ? Regards, Vlad PS Feel free to contact me privately, if necessary ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
