Insane cpu usage by zmmailboxd

[matteo.fracassetti]

A collegue of mine made some deep investigations and he may have found the issue...

We use z-push to allow our users to access to their mailbox through ActiveSync. Into the logs we noticed that one e-mail was causing a mailloop while syncing: It happens quite often but usually z-push is able to address the issue by itself. But while z-push was trying to solve the loop, in zmmailboxd.out appears some messages like this:

2018-03-22 16:19:56.521:INFO:oejm.ThreadMonitor:Thread-52: Thread 'qtp1286783232-336:http://our.server.url/service/soap/'[RUNNABLE,id:336,cpu:99.79%] SPINNING

With zmthrdump he discovered that thread was in state "RUNNABLE" and was locked by something concerned to "java.util.regex".

With some more debugging he was able to identify the e-mail which was causing the issue and he tried to open it through the zimbra web interface... And it crashes.
So we move that email out from the mailbox and restarted mailboxd, after that we don't notice CPU spikes anymore.

The email was a normal commercial email sent from Tustena_CRM throught Microsoft cloud infrastructure, with tons of headers and bloat code in it but nothing of so unusual.

It seems related to this issue, again: https://bugzilla.zimbra.com/show_bug.cgi?id=101227

[msquadrat]

Are you able to share the bad mail with us so we can try to reproduce the issue? Please contact me via PM if you can share it in private only and I'll see if I can create a test case from the mail.

[matteo.fracassetti]

Sure.
I'll send it to you in some minutes.

[L. Mark Stone]

I'd be happy to test as well.

If the test proves reproducible, then we can open a new support case as a first step to getting developer attention on this.

Thanks!
Mark

[unaiSolaguren]

Hi matteo.

¿Did you test this paremeter in z-push?

config.php: define('SYNC_FILTERTIME_MAX', SYNC_FILTERTYPE_2WEEKS);

Accounts with high number of folders and big mailboxes generete high cpu use.

[matteo.fracassetti]

Hi, thank you for your suggestion.

The issue is definitively due to that email I talk about some posts ago: I sent it to users msquadrat for testing some times ago (to L. Mark Stone I sent it only today due to a misunderstading)... I would be courious to know if they has been able to reproduce the issue.

[7224jobe]

Maybe Patch 2 for Zimbra 8.7.11 that was just released will help with similar issues, since it fixes this bug: https://bugzilla.zimbra.com/show_bug.cgi?id=108928

Here is the patch announcement: https://wiki.zimbra.com/wiki/Zimbra_Rel ... i=62062265