Using the Admin Console I selected an account and clicked on the view webmail button. As normal a new window popped open and after the inital zimbra loading screen finished and error popped up that said "No such conversation exists"
Here is the output
Any ideas??
msg - no such conversation: -1
com.zimbra.cs.mailbox.MailServiceException$NoSuchItemException: no such conversation: -1
at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH_CONV(MailServiceException.java:120)
at com.zimbra.cs.mailbox.MailItem.noSuchItem(MailItem.java:752)
at com.zimbra.cs.db.DbMailItem.getById(DbMailItem.java:1121)
at com.zimbra.cs.mailbox.MailItem.getById(MailItem.java:703)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox.java:1692)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox.java:1661)
at com.zimbra.cs.mailbox.Mailbox.getConversationById(Mailbox.java:2157)
at com.zimbra.cs.index.ConversationHit.getConversation(ConversationHit.java:191)
at com.zimbra.cs.service.mail.Search.addConversationHit(Search.java:310)
at com.zimbra.cs.service.mail.Search.putHits(Search.java:267)
at com.zimbra.cs.service.mail.Search.handle(Search.java:117)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:249)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:163)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:84)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:226)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:526)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
code - mail.NO_SUCH_CONV
method - ZmCsfeCommand.prototype.invoke
detail - soap:Sender
Corrupted Mailbox
-
14319KevinH
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Corrupted Mailbox
Hi Matt, Is this something you can reproduce everytime? Does it also happen if you just login directly to the user's inbox?
Corrupted Mailbox
Hey Kevin.
It appeared to be only via the administration console, and i tried it on a few users and it was hit and miss, (NOTE i also noticed if you do not implicitly logout of the session no matter who's email it will cache the login session so I dont believe i was getting an acurate view of who this was effecting.)
In any event, with no intervention from myself it appears to have fixed itself. I can now log in via administrative console and via zimbra webmail with out any problems. If problems persist i'll let you know
It appeared to be only via the administration console, and i tried it on a few users and it was hit and miss, (NOTE i also noticed if you do not implicitly logout of the session no matter who's email it will cache the login session so I dont believe i was getting an acurate view of who this was effecting.)
In any event, with no intervention from myself it appears to have fixed itself. I can now log in via administrative console and via zimbra webmail with out any problems. If problems persist i'll let you know
-
tim brennan
- Advanced member
- Posts: 93
- Joined: Fri Sep 12, 2014 9:55 pm
Corrupted Mailbox
This sounds like the same issue as Bug 4033 and Bug 4909. In those cases, a message in the message cache has an invalid conversation ID for some reason -- even though the on-disk version of the message is fine.
We think this is some kind of a race condition either with IMAP or with the MAPI connector (Network Edition only) --- can you tell me if the affected account was using either of these? How about POP3?
Since the conversation ID is only corrupted in the in-memory cache, you can fix the account by forcing the cache to reload: the message cache is a max of 500 messages (per account) and so paging through other folders will do it...alternatively, as a last resort bouncing your server should also fix the problem.
We think this is some kind of a race condition either with IMAP or with the MAPI connector (Network Edition only) --- can you tell me if the affected account was using either of these? How about POP3?
Since the conversation ID is only corrupted in the in-memory cache, you can fix the account by forcing the cache to reload: the message cache is a max of 500 messages (per account) and so paging through other folders will do it...alternatively, as a last resort bouncing your server should also fix the problem.