Hey Andrii,

2009/5/19 Andrii Arsirii <[email protected]>:
> Hi, Koen.
>
> You can find fix for this bug in attachment.

Thanks a lot.

> Please review.
>
> Note that we can't use a mutex to protect sessionProcessPids_, because we
> can't lock mutex from signal handler.
> The reason is that the OS returns control to userspace code only after it
> executes its signal handlers (at least freebsd and linux do so).
> And if userspace code (wt application) locks and sleeps on mutex and later
> the same mutex is locked from the signal handler, we'll be stuck forever.

Yes, I got that.

Do you know why the shared session processed die however? I also saw
in the code that only 5 times a shared session process is respawned
before giving up entirely. I would imagine that you may run into that
problem then as well ?

Anyway, I fixed the code along the lines that you suggested... It will
be in the public git soon.

Regards,
koen

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to