Este problema es por que el servidor se esta recibiendo una mayor cantidad de conexiones imap/pop/lmpt que puede procesar, generando que el servicio mailbox se caiga.
Error:
Oct 31 10:34:48 localhost.localdomain mailboxd: WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 105% utilized. 21 out of 20 threads in use.
Oct 31 10:34:48 localhost.localdomain mailboxd: ERROR [LmtpServer] [] TcpServer/7025 - cannot handle connection; thread pool exhausted
Oct 31 10:34:48 localhost.localdomain at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
Oct 31 10:34:48 localhost.localdomain at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
Oct 31 10:34:48 localhost.localdomain at com.zimbra.cs.tcpserver.TcpServer.run(TcpServer.java:202)
Oct 31 10:34:48 localhost.localdomain at java.lang.Thread.run(Thread.java:662)
Oct 31 10:34:48 localhost.localdomain mailboxd: WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 105% utilized. 21 out of 20 threads in use.
Solución
Básicamente es incrementar los parámetros que administran este tipo de conexiones, dejándolo así:
[zimbra@apolo ~]$ zmprov mcf zimbraImapNumThreads 500
[zimbra@apolo ~]$ zmprov mcf zimbraPop3NumThreads 300
[zimbra@apolo ~]$ zmprov mcf zimbraLmtpNumThreads 40
[zimbra@apolo ~]$ zmprov mcf zimbraHttpNumThreads 500
Reiniciamos el servicio mailbox
[zimbra@apolo] zmmailboxdctl restart
0 Comentarios