|Subject||Re: GUI version of FB Trace Manager (fbtracemgr)|
> > The only problem that I have at the moment is that I am using the "isc_info_svc_timeout" command as part of a "isc_info_svc_line" isc_service_query() but instead of replying with "isc_info_svc_timeout" in the header the server replies with "isc_info_svc_line" but a zero length data block.This might be my misunderstanding of the "service was stopped at the server side" but after receiving isc_info_svc_line + 0 I continue to receive isc_info_svc_line + valid data as soon some traceable event occurs so I don't think it has stopped?
> IIRC, isc_info_svc_line (or isc_info_svc_to_eof) + zero data length means end of stream and service was stopped at server side.
Although I am running the query in a thread I need the timeout because
isc_service_query() blocks until it is ready to send some data otherwise.
>Thanks for the tip, I will try to re-write to use isc_info_svc_to_eof.
> BTW, fbtracemgr used isc_info_svc_to_eof query, not isc_info_svc_line. The latter will produce very low performance.
> Because it is not an error. Errors reported via status-vector :)
>Thanks I will do, it might take me some time because I am still learning, but I wanted to thank you for your reply quickly first.
> Re-read TraceSvcUtil::runService() carefully...