Everyday, I end up deleting over 1000 errors and they seem to be the same one. Here a sample of the error and I have reported this but I have seen no more updates or resolutions.
Product name: Zimbra Desktop
Product version: 0.91
Build ID: 1338
Release type: BETA
OS Platform: Windows Vista x86 6.0
Time of event: 2008-10-31 10:06:51
Error type: service.FAILURE
Error summary: Synchronization of folder 'INBOX.Internal.Miguel Galdames' failed. Synchronization has been disabled for this folder
Failure details:
----------------------------------------------------------------------------
com.zimbra.common.service.ServiceException: system failure: Unable to store IMAP message data
ExceptionId:btpool0-21:1225465611469:e0dc7e55025b90cb
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
at com.zimbra.cs.db.DbImapFolder.createImapFolder(DbImapFolder.java:111)
at com.zimbra.cs.account.DataSource.createImapFolder(DataSource.java:331)
at com.zimbra.cs.datasource.ImapFolderSync.createLocalFolder(ImapFolderSync.java:434)
at com.zimbra.cs.datasource.ImapFolderSync.syncFolder(ImapFolderSync.java:112)
at com.zimbra.cs.datasource.ImapSync.syncRemoteFolders(ImapSync.java:176)
at com.zimbra.cs.datasource.ImapSync.syncFolders(ImapSync.java:157)
at com.zimbra.cs.datasource.ImapSync.importData(ImapSync.java:120)
at com.zimbra.cs.datasource.DataSourceManager.importData(DataSourceManager.java:158)
at com.zimbra.cs.mailbox.LocalMailbox.importData(LocalMailbox.java:354)
at com.zimbra.cs.mailbox.LocalMailbox.syncAllLocalDataSources(LocalMailbox.java:327)
at com.zimbra.cs.mailbox.LocalMailbox.sync(LocalMailbox.java:383)
at com.zimbra.cs.service.offline.OfflineSync.handle(OfflineSync.java:46)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:411)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:268)
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:189)
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: java.sql.SQLException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL080910175843140' defined on 'IMAP_FOLDER'.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:233)
at com.zimbra.cs.db.DbImapFolder.createImapFolder(DbImapFolder.java:106)
... 37 more
Caused by: ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL080910175843140' defined on 'IMAP_FOLDER'.
at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.doInsert(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexChanger.insert(Unknown Source)
at org.apache.derby.impl.sql.execute.IndexSetChanger.insert(Unknown Source)
at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(Unknown Source)
at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(Unknown Source)
at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
... 42 more
----------------------------------------------------------------------------
Quantity of errors is killing me
Quantity of errors is killing me
Could you please file a bug report and include log/zdesktop.log as a private attachment? Also, if its possible, please go to account setup and enabled "Debug Trace" and attach log/zdesktop.out as well. This will show us a trace of the IMAP commands leading to the error so we can better determine what is happening and hopefully can give you a workaround soon!
Thanks,
David
Thanks,
David