SW Test Automation Framework

I'm assuming the workaround that Charles described will work for your
handle logs.
I'm closing this bug.

I think that somewhere in the feature list is a feature to not have
handles restart at 1 when STAFProc restarts. Obviously, we haven't gotten
to that one yet. :) Even still, that won't technically solve your problem
as handle numbers would ultimately exceed the size of an unsigned int on
the platform and rollover, generating the same problem (albeit with much
much less frequency).

The STAX service has to deal with a similar problem, as Job numbers there
restart with 1 whenever STAX is restarted. What we do there is have every
job log a START (level) message at the beginning of the job. This makes it
easy to determine where in the log a specific "run" occured. I would
suggest you do something similar. It wouldn't have to be a START level
message, just some message that you can use to determine the beginning of a
specific process' run. With that indicator, you can find the LAST one of
them, get that log record number and query for all the records starting
from that one.

For me, and I suppose for other people this behaviour becomes a problem.
I mean:
- I start a process with STAFProcess service... and I get a handle. I
create a LOG HANDLE queue with the same handle of the process in order to
be able to show specific logs for this process only.
- If I restart STAFProc, as you say, the handle assignation starts id 1
again. The LOG handle still exists and because LOGS are not removed when
STAFProc restarts.
If I get a new handle for a new process, and this handle matchs with
another handle that I have got before STAFProc restarts, the new LOG HANDLE
contains both log queues.
What I suggest is that you can't not use a handle that has been assigned
before and it has a LOG handle associate yet.
I'll be greatful if you can give me a workaruond.
Thanks.

This is not a bug. This is working as designed. Once STAFProc has been
shutdown, then STAF no longer knows about any processes that were
previously started via STAF. When STAFProc is re-started, it resets the
handle numbers it uses to start with handle id 1 and does not know about
any processes that were previously started via STAF.

Perhaps if you described what it is that you are trying to do where this
feature is causing a problem for you, we could suggest a solution for you.