>> I could simply use the entire snapshot build and sync the moving parts like
>> security database, conf files, UDFs etc. or perhaps I could simply replace a
>> single (executable) file (firebird.exe?) taken from the snapshot ZIP file?
>>
>
> Not firebird.exe but engine12.dll.
Thanks!
Thomas
> I could simply use the entire snapshot build and sync the moving parts like
> security database, conf files, UDFs etc. or perhaps I could simply replace a
> single (executable) file (firebird.exe?) taken from the snapshot ZIP file?
>
Not firebird.exe but engine12.dll.
>> 21.04.2016 13:35, Thomas Steinmaurer wrote:
>> ...
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 ?
>>>
>>> The usage of
> 21.04.2016 13:35, Thomas Steinmaurer wrote:
> ...
>>> 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 ?
>>
>> The usage of the trace
> 21.04.2016 13:35, Thomas Steinmaurer wrote:
> ...
>>> 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 ?
>>
>> The usage of the trace
21.04.2016 13:35, Thomas Steinmaurer wrote:
...
>>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 ?
>
> The usage of the trace services in FBTM
> On 04/21/2016 12:47 PM, Thomas Steinmaurer wrote:
>> Hi Alex,
>>
> Hello Vlad,
>
>>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>>> ...
What else could I provide so that you can investigate the offending
thread?
>>> Full memory dump, please.
> Have
On 04/21/2016 12:47 PM, Thomas Steinmaurer wrote:
> Hi Alex,
>
Hello Vlad,
>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>> ...
>>> What else could I provide so that you can investigate the offending
>>> thread?
>> Full memory dump, please.
Have you had time
Hello Vlad,
>>> 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
Hi Alex,
>>> Hello Vlad,
>>>
> 20.04.2016 0:47, Thomas Steinmaurer wrote:
> ...
>> What else could I provide so that you can investigate the offending
>> thread?
> Full memory dump, please.
>>> Have you had time to look at it?
>>>
>>> Unfortunately this now also has
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
On 04/21/2016 12:00 PM, Thomas Steinmaurer wrote:
> Hi again,
>
>> Hello Vlad,
>>
20.04.2016 0:47, Thomas Steinmaurer wrote:
...
> What else could I provide so that you can investigate the offending
> thread?
Full memory dump, please.
>> Have you had time to look at it?
Hi again,
> Hello Vlad,
>
>>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>>> ...
What else could I provide so that you can investigate the offending
thread?
>>>
>>>Full memory dump, please.
>
> Have you had time to look at it?
>
> Unfortunately this now also has happened in a
Hello Vlad,
>> 20.04.2016 0:47, Thomas Steinmaurer wrote:
>> ...
>>> What else could I provide so that you can investigate the offending
>>> thread?
>>
>>Full memory dump, please.
Have you had time to look at it?
Unfortunately this now also has happened in a production environment at
a
Vlad,
> 20.04.2016 0:47, Thomas Steinmaurer wrote:
> ...
>> What else could I provide so that you can investigate the offending
>> thread?
>
> Full memory dump, please.
I'm not that familiar with WinDbg and played around with it.
The stack trace of the high CPU thread is, I think:
#
Hello Vlad,
> 20.04.2016 0:47, Thomas Steinmaurer wrote:
> ...
>> What else could I provide so that you can investigate the offending
>> thread?
>
> Full memory dump, please.
I have been using sysinternals procdump for that with:
procdump -ma
Is this what you are looking for?
It is
20.04.2016 0:47, Thomas Steinmaurer wrote:
...
> What else could I provide so that you can investigate the offending
> thread?
Full memory dump, please.
Regards,
Vlad
--
Find and fix application performance issues
Hello,
first of all, congratulations to Firebird 3.
I'm basically seeking for assistance pin-pointing an issue here with
Firebird 3 SuperServer 32-bit on Windows 10 Prof., as it seems, in the
context of the Trace API. This all is not an issue with Firebird 2.5.
Unfortunately, it is only
18 matches
Mail list logo
