Hi,
We've taken a completely different approach. We only create threads at startup
and then have them checkin to the watchdog. Resource usage is more
deterministic (when compared to dynamically creating threads) and there is less
work required on each new web request. We don't need a thread monitor or know
or care about the thread id.
...Laurie:{)
On 28/03/2012, at 12:12 AM, Quanren Xiong <xion...@gmail.com> wrote:
> Hi,
>
> We are running a web server on our ECOS plaform. It spawns a thread
> each time a web request comes in.
> We found that afte a while the thread unique id would wrap around.
> An id that is being used by a running thread would be re-used.
> Our thread monitor which keeps track of running thread by their ids
> would assert because it sees duplicate ids.
>
> Anyone have any suggestions or solutions. Thank you very much.
>
>
> Regards,
>
> Q Xiong
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
