Results 1 to 3 of 3

Thread: LmtpServer thread pool exhausted

Hybrid View

  1. #1
    Join Date
    Jul 2009
    Rep Power

    Default LmtpServer thread pool exhausted

    Since upgrading to zimbra 7 we've had our lmtp thread pool exhausted 3 times on our two mailbox servers. There doesn't appear to be any large burst of email and the mailbox servers don't have a high load while its happening. Some details:

    Release 7.1.1_GA_3196.RHEL5_64_20110527001604 RHEL5_64 NETWORK edition
    5 zimbra servers (1 ldap, 2 proxy, 2 mailbox)

    Here is the error I see in the /opt/zimbra/log/maillog.log file when the issue starts happening:

    2011-08-03 22:43:11,048 WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 100% utilized. 20 out of 20 threads in use.
    2011-08-03 22:43:30,240 WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 100% utilized. 20 out of 20 threads in use.
    2011-08-03 22:55:03,157 WARN [LmtpServer] [] TcpServer/7025 - Thread pool is 105% utilized. 21 out of 20 threads in use.
    2011-08-03 22:55:03,157 ERROR [LmtpServer] [] TcpServer/7025 - cannot handle connection; thread pool exhausted
    at java.util.concurrent.ThreadPoolExecutor$AbortPolic y.rejectedExecution(
    at java.util.concurrent.ThreadPoolExecutor.reject(Thr
    at java.util.concurrent.ThreadPoolExecutor.execute(Th
    at va:202)

    This continued until I did a reload on the mailboxdctrl on that server. While this happened the proxy/mta server queued up ~1000 emails (not a huge number). When I found it this morning the load on the mailbox server was only 0.54, 0.57, 0.46 and wasn't having any IO issues that I saw. After the reload of mailboxd I requeued the emails on the mta and they all delivered without any issue within a very short amount of time. This leads me to believe it might be something with threads being locked by something or maybe some sort of thread "garbage collection" not working?

    Something else to note....when it first starting happening last night I aslo saw this in the log which I don't remember seeing in version 6 when users were over quota:

    2011-08-03 22:43:11,439 ERROR [LmtpServer-3607] [;mid=943;ip=xxxxx;] jsieve - Evaluation failed. Reason: null
    2011-08-03 22:43:11,439 WARN [LmtpServer-3607] [;mid=943;ip=xxxxxxx;] filter - An error occurred while processing filter rules. Filing message to /Inbox.
    Caused by: com.zimbra.cs.mailbox.MailServiceException: mailbox exceeded quota of 1048576000 bytes
    Code:mail.QUOTA_EXCEEDED Arglimit, NUM, "1048576000")
    at com.zimbra.cs.mailbox.MailServiceException.QUOTA_E XCEEDED(

    I've just upped the thread pool from 20 to 40 to see if that helps.

    Any other thoughts on what could be causing this or how to fix it?

  2. #2
    Join Date
    Dec 2011
    Rep Power


    cayaraa, I am experience the same symptoms you have noted on one of my boxes and am curious if increasing zimbraLmtpNumThreads to 40 helped your concern.


  3. #3
    Join Date
    Jul 2009
    Rep Power


    IIRC it did help but shortly after this we realized that our local drives that held the zimbra application data was being maxed out (iops wise) as apposed to the data store/index drives that we had been focusing on. We had a hunch that the thread pool errors might have been an early symptom of this but didn't have any way to know for sure.

Similar Threads

  1. thread pool exhausted (IMAP)
    By rgiapratama in forum Administrators
    Replies: 2
    Last Post: 05-20-2013, 05:09 AM
  2. Replies: 0
    Last Post: 02-16-2011, 06:44 PM
  3. Services stopping randomly
    By caio80 in forum Administrators
    Replies: 18
    Last Post: 04-23-2008, 04:59 PM
  4. postfix stopped
    By riegersteve in forum Administrators
    Replies: 1
    Last Post: 05-15-2007, 03:25 PM
  5. Can't start Zimbra!
    By zibra in forum Administrators
    Replies: 5
    Last Post: 03-22-2007, 11:34 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts