Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Desktop > Error Reports

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-14-2010, 12:23 PM
Junior Member
 
Posts: 7
Default Failure communicating with remote server. Please try again later.

From an install of zdesktop_2_0_b10580_win32.msi, I was able to add a Zimbra account connecting to zcs-NETWORK-6.0.6_GA (patched) without any problem. When I added another Zimbra account connecting to zcs-6.0.7_GA_2470 (open source), it downloaded all of the mail and calendar events, but now it can't sync new messages. The error message follows:

Code:
Debug message: Java heap space

Exception:

java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOfRange(Unknown Source)
    at java.lang.String.(Unknown Source)
    at java.lang.StringBuilder.toString(Unknown Source)
    at net.fortuna.ical4j.data.CalendarParserImpl.parseProperty(CalendarParserImpl.java:263)
    at net.fortuna.ical4j.data.CalendarParserImpl.parsePropertyList(CalendarParserImpl.java:196)
    at net.fortuna.ical4j.data.CalendarParserImpl.parseComponent(CalendarParserImpl.java:355)
    at net.fortuna.ical4j.data.CalendarParserImpl.parsePropertyList(CalendarParserImpl.java:193)
    at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendar(CalendarParserImpl.java:161)
    at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendarList(CalendarParserImpl.java:133)
    at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:94)
    at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.parse(ZCalendar.java:920)
    at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.buildMulti(ZCalendar.java:894)
    at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.build(ZCalendar.java:878)
    at com.zimbra.cs.mime.handler.TextCalendarHandler.analyze(TextCalendarHandler.java:77)
    at com.zimbra.cs.mime.handler.TextCalendarHandler.getICalendar(TextCalendarHandler.java:52)
    at com.zimbra.cs.mime.ParsedMessage.analyzePart(ParsedMessage.java:1101)
    at com.zimbra.cs.mime.ParsedMessage.analyzeNonBodyParts(ParsedMessage.java:433)
    at com.zimbra.cs.mime.ParsedMessage.analyzeFully(ParsedMessage.java:467)
    at com.zimbra.cs.mailbox.CalendarItem.getIndexDocuments(CalendarItem.java:342)
    at com.zimbra.cs.mailbox.CalendarItem.generateIndexData(CalendarItem.java:218)
    at com.zimbra.cs.mailbox.IndexHelper.indexItemList(IndexHelper.java:848)
    at com.zimbra.cs.mailbox.IndexHelper.indexDeferredItemsInternal(IndexHelper.java:367)
    at com.zimbra.cs.mailbox.IndexHelper.indexDeferredItems(IndexHelper.java:284)
    at com.zimbra.cs.mailbox.IndexHelper.maybeIndexDeferredItems(IndexHelper.java:240)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:4341)
    at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:4334)
    at com.zimbra.cs.mailbox.InitialSync.saveMessage(InitialSync.java:1207)
    at com.zimbra.cs.mailbox.InitialSync.syncMessagesAsTgz(InitialSync.java:1027)
    at com.zimbra.cs.mailbox.InitialSync.syncMessages(InitialSync.java:960)
    at com.zimbra.cs.mailbox.InitialSync.syncMessagelikeItems(InitialSync.java:433)
    at com.zimbra.cs.mailbox.InitialSync.initialFolderSync(InitialSync.java:323)
    at com.zimbra.cs.mailbox.InitialSync.prioritySync(InitialSync.java:397)
Reply With Quote
  #2 (permalink)  
Old 10-14-2010, 12:27 PM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

WHat operating system is this installed on and how much RAM is on the machine?
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 10-14-2010, 12:38 PM
Junior Member
 
Posts: 7
Default

The client machine is Windows XP SP3 with 3G of RAM.
Reply With Quote
  #4 (permalink)  
Old 10-22-2010, 06:31 AM
Trained Alumni
 
Posts: 193
Default

I'm getting the same error on Windows 7 64-bit.
Reply With Quote
  #5 (permalink)  
Old 10-22-2010, 12:42 PM
Zimbra Employee
 
Posts: 98
Default

At first glance it looks like you have an appointment request in your mailbox which is rather large; too large for our default heap size settings so we are running out of heap when trying to parse it.

You can try increasing the maximum heap size in <ZD data>/conf/zdesktop.conf. You should find a line that looks like this:

java.arg.4=-Xmx120m

Change the value to -Xmx256m, save, and then restart ZD and try again. Since you are on Windows; when restarting be sure to select Quit from the system tray icon.

If that doesn't work, try 512 and so on. Please let us know what value works for you, or if this doesn't help.

<ZD data> can be found at:

Mac: ~/Library/Zimbra Desktop

Linux: ~/zdesktop

Windows XP: C:\Documents and Settings\<user>\Local Settings\Application Data\Zimbra\Zimbra Desktop

Windows 7/Vista: C:\Users\<user>\AppData\Local\Zimbra\Zimbra Desktop
Reply With Quote
  #6 (permalink)  
Old 11-01-2010, 10:41 AM
Member
 
Posts: 14
Default Failure communicating with remote server. Please try again later. Reply to Thread

I have the same issue as well. A e-mail with large attachments seems to be stuck. I get the following error:

Failure communicating with remote server. Please try again later.

Debug message: Java heap space

Exception:

java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Unknown Source)
at java.io.ByteArrayOutputStream.write(Unknown Source)
at com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtili ty.java:256)
at javax.mail.internet.MimeMessage.parse(MimeMessage. java:335)
at javax.mail.internet.MimeMessage.(MimeMessage.java: 205)
at com.sun.mail.handlers.message_rfc822.getContent(me ssage_rfc822.java:98)
at javax.activation.DataSourceDataContentHandler.getC ontent(Unknown Source)
at javax.activation.DataHandler.getContent(Unknown Source)
at javax.mail.internet.MimeBodyPart.getContent(MimeBo dyPart.java:630)
at com.zimbra.cs.mime.Mime.getMessageContent(Mime.jav a:410)
at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor. java:231)
at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor. java:213)
at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor. java:176)
at com.zimbra.cs.mime.ExpandMimeMessage.expand(Expand MimeMessage.java:86)
at com.zimbra.cs.mime.ParsedMessage.init(ParsedMessag e.java:286)
at com.zimbra.cs.mime.ParsedMessage.initialize(Parsed Message.java:229)
at com.zimbra.cs.mime.ParsedMessage.initialize(Parsed Message.java:193)
at com.zimbra.cs.mime.ParsedMessage.(ParsedMessage.ja va:140)
at com.zimbra.cs.mime.ParsedMessage.(ParsedMessage.ja va:135)
at com.zimbra.cs.mailbox.CalendarItem.storeUpdatedBlo b(CalendarItem.java:2057)
at com.zimbra.cs.mailbox.CalendarItem.createBlob(Cale ndarItem.java:2122)
at com.zimbra.cs.mailbox.CalendarItem.create(Calendar Item.java:486)
at com.zimbra.cs.mailbox.Mailbox.createCalendarItem(M ailbox.java:5691)
at com.zimbra.cs.mailbox.Mailbox.setCalendarItem(Mail box.java:3775)
at com.zimbra.cs.mailbox.InitialSync.setCalendarItem( InitialSync.java:846)
at com.zimbra.cs.mailbox.InitialSync.syncCalendarItem (InitialSync.java:652)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:267)
at com.zimbra.cs.mailbox.InitialSync.prioritySync(Ini tialSync.java:397)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:377)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:387)
at com.zimbra.cs.mailbox.InitialSync.resume(InitialSy nc.java:198)
at com.zimbra.cs.mailbox.InitialSync.resume(InitialSy nc.java:182)

If issue persists please post description and debug information here.


I have changed the Xmx= 256, 512, 1024, 2048m and I still get the same message.

Zimbra Desktop 2, on Ubuntu 10.04 x64, 4gb ram
ZCS 6 on Centos.

Mark
Reply With Quote
  #7 (permalink)  
Old 11-05-2010, 10:24 AM
Zimbra Employee
 
Posts: 98
Default

On Linux you'll need to change the Xmx in bin/zdesktop under your user data directory (typically /home/<user>/zdesktop).

You should find a MAILBOXD_JAVA_OPTIONS property around line 298.

To make sure you're actually affecting the runtime, you can do a ps -eaf | grep zimbra and note the XmX option displayed.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.