Vlad,
Try increasing your per-thread stack size and see if the problem goes
away. If a thread uses more of its stack than it is supposed to, it
corrupts other thread stacks which usually leads to the server
getting stuck. The parameter to do this is below:
ns_param stacksize [expr 128*1
On 2007.07.03, Vlad Hociota <[EMAIL PROTECTED]> wrote:
> The problem is the first thread in line is waiting on the condition
> variable, but the thread that it is supposed to join no longer exists
> (or so does the core file state). Hence we get the deadlock.
It looks like the server is in the pro
Hello folks.
I'm digging into this issue and thought maybe someone might remember
anything from those days .
The piece of software is a server based on AOL-3.4 code, but with some
proprietary modules added on top.
The issue cannot be reproduced in a repetitive way -- but sometimes we
find
