There is probably an event in his calendar that somehow got corrupted on server.
Can you turn on Debug Logging (Account Setup...) and try to figure out which event was causing the problem by looking at the "SOAP requests" captured in log/zdesktop.log, when it runs out of memory? (if you attach the log/zdesktop.log, we may help you to locate the event)
Once you know which event is causing this, you can login using web client to delete it and recreate it if needed.
Quote:
Originally Posted by iskondi  Hey there guys,
I've been using Zimbra Desktop for quite awhile and have been very happy with it. Another employee wanted to start testing it as well and we immediately ran into a problem.
The sync of his mailbox starts but then dies with the bellow error message at the end of the log.
Now I already looked and saw that this was "fixed" for a previous iteration but I'm now running into it again running the latest version of Zimbra Desktop.
Any ideas? Can I post more information that would be helpful?
Directly before this message it appears to be syncing the calendar, and the behavior is you see the zdesktop.exe process use more and more memory until roughly 315MB when it dies.
Originally this employee was running it on his machine with 1GB of memory, so we figured it was memory and upped his memory to 1.5GB which had no affect.
Then I decided to try it on my machine which has 4GB of memory and the SAME EXACT issue! Something specific with his mailbox but what and how to fix it?
Thanks,
Iskondi
2009-03-10 13:12:33,380 FATAL [mid=5] [mid=5;] system - Caught out of memory error
java.lang.OutOfMemoryError: Java heap space
at com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtili ty.java:240)
at javax.mail.internet.MimeMessage.parse(MimeMessage. java:325)
at javax.mail.internet.MimeMessage.<init>(MimeMessage .java:196)
at com.zimbra.cs.mime.Mime$FixedMimeMessage.<init>(Mi me.java:140)
at com.zimbra.cs.service.mail.ParseMimeMessage.import MsgSoap(ParseMimeMessage.java:109)
at com.zimbra.cs.service.mail.SetCalendarItem.getSetC alendarItemData(SetCalendarItem.java:151)
at com.zimbra.cs.service.mail.SetCalendarItem.parseSe tAppointmentRequest(SetCalendarItem.java:209)
at com.zimbra.cs.mailbox.InitialSync.setCalendarItem( InitialSync.java:801)
at com.zimbra.cs.mailbox.InitialSync.syncCalendarItem (InitialSync.java:679)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:264)
at com.zimbra.cs.mailbox.InitialSync.prioritySync(Ini tialSync.java:394)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:374)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:384)
at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync .java:171)
at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync .java:154)
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync .java:180)
at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineM ailbox.java:140)
at com.zimbra.cs.mailbox.OfflineMailbox.syncOnTimer(O fflineMailbox.java:121)
at com.zimbra.cs.mailbox.DesktopMailbox$1.run(Desktop Mailbox.java:436)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source) |