On 08/21/2013 09:53 AM, David Boreham wrote:
Another thing you might try :
While the server is under stress, run the "pstack" command a few times
and save the output.
gdb will give much more detail
http://port389.org/wiki/FAQ#Debugging_Hangs
If you post the thread stacks here, someone familiar with the code can
say with more accuracy what's going on. For example it will be obvious
whether you have starved out the thread pool, or you have threads
mostly waiting on page locks in the DB, etc.
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-us...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
