Quote:
Originally Posted by uxbod have you tried Code: ps aux | grep zimbra and look through the process list to see what is actually running ? |
Sorry to awaken an old thread, but you need other arguments to ps in order to see the number of threads. On Red Hat, ps -eLf is nice, and pstree will count the threads for you (maybe mixing threads and processes, but in this case that's fine).
Hitting zimbraHttpNumThreads can be a problem, as there are no explicit errors in logs. Zimbra just stops replying to requests, and logs only mention "localhost failed to respond".
I would have liked having the period's high-water mark of pool usage in the zmcharts. That seemingly simple measure would have saved me and my employer some ten hours accumulated downtime, a lot of snide remarks and ill will from users, and quite serious questions from management in the style "why did you choose this product if it's unstable".
FWIW we started hitting 250 threads at about 4000 logged-in users, presumably all back from Christmas holidays catching up on their mail.