Since at least some of you are on CentOS 6 - I wonder if this issue is also at the root of your problems. I have seen java consume all CPU on my windows desktop/firefox using several of the most recent java releases up until I disabled ipv6 bit networking support. http://www.zimbra.com/forums/adminis...end-users.html
...got the same problem today with two fresh installed virtual appliances (v. 8.0.2) :-( ...any ideas? rebooting or killing the process doesn't help.
is it just pure fresh install without any mailboxes? Or have you try to import/restore mailboxes from your old server?
What's the operating system you use?
The java process came up with > 100% when i migrated the first data... Yesterday night i found out that the following action triggers it:
I connected my mac os x (10.8.2) address book (over CardDav) to the old zimbra server (V.7) and to the new installed (8.0.2 virtual appliance). Then i moved (drag-and-drop) around 120 contacts from the old to the new server (directly in die address book app on my mac). Result: java process goes up to 180% and stays there for a long time :-)
my guess: it is something with the pictures in my contacts... do you guys have the same issue?`
Yes, I would say this is quite common. It happened to us mainly during imports, exports are usually fine. Depending on the import, the java process will spike to 100% from few minutes to hours.
Because of this, we don't use Zimbra tools (command line) for import/export anymore.
We use ZeXtras tools or simply Zimbra Desktop. We'll create a new account first, configure it in the Zimbra desktop, import the stuff there and then let it sync to server. This works well if you used Zimbra server before, which is your case and it won't cause any java spikes.
I truly recommended ZeXtras for any migrations and backup/restore. There is nothing better than what ZeXtras team did for the whole Zimbra community. They have actually made Zimbra useable to wide public.
And no, I don't work for ZeXtras. We are just a happy user and support everything they do.
I'm having this exact same problem. I upgraded from 7.2.2 to 7.2.3 about a month ago and we are getting this constantly.
Originally Posted by cadi-its
Here's the output from top -c
What is the fix for this? I see lots of reports of this issue, but no fixes. The only thing I do see is that this problem existed in 7.1.x and there was a patch in 7.1.4.
16510 zimbra 20 0 1869m 1.4g 11m S 1 29.8 470:06.18 /opt/zimbra/java/bin/java -Dfile.encoding=UTF-8 -server -Djava.awt.headless=true -Dsun.net.inetaddr.ttl=60 -XX:+UseConcMarkSweepGC -XX:PermSize