-
Briefcase problems
Has anyone seen these issues with ZD RC2 (build 1513)?
Running under Mac OS 10.5, by the way.
1. If I try to upload a file that's larger than what's allowed under Global Settings:General Information in the admin interface, ZD doesn't warn me and seems to upload the file, but it's not accessible from other login instances (e.g. web client).
2. After that happens, the list of contents in each briefcase within ZD doesn't seem to be accurate.
It doesn't look like the file is really uploaded; ZWC's quota info doesn't show any increase in usage.
Status icon in ZD turns to red circle with exclamation point. Tooltip shows status: error.
Going into the setup screen, I get "Failure communicating with remote server. Please try again later." with debug link.
Debug link gives me: Code:
Debug message: resource unreachable: system failure native formatter failure
Exception:
com.zimbra.common.service.ServiceException: system failure: PushChanges.sync
ExceptionId:btpool0-5:1236748903614:c38ccf80af99dbef
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
at com.zimbra.cs.mailbox.SyncExceptionHandler.checkRecoverableException(SyncExceptionHandler.java:40)
at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:373)
at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:174)
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync.java:185)
at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineMailbox.java:140)
at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:47)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:429)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:269)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: com.zimbra.common.service.ServiceException: resource unreachable: system failure native formatter failure
ExceptionId:btpool0-5:1236748903614:c38ccf80af99dbef
Code:service.RESOURCE_UNREACHABLE
at com.zimbra.common.service.ServiceException.RESOURCE_UNREACHABLE(ServiceException.java:275)
at com.zimbra.cs.service.UserServlet.doHttpOp(UserServlet.java:1447)
at com.zimbra.cs.service.UserServlet.putMailItem(UserServlet.java:1369)
at com.zimbra.cs.mailbox.OfflineMailbox.sendMailItem(OfflineMailbox.java:812)
at com.zimbra.cs.mailbox.PushChanges.syncDocument(PushChanges.java:1069)
at com.zimbra.cs.mailbox.PushChanges.sync(PushChanges.java:370)
... 30 more
Deleting the file in ZD fixes the problem.
-
