Can't open folder

[Russianspi]

Hi. I have a user who is trying to open up his "Sent" folder, and can't. I logged in as him at a different location, using a different OS, and got the same result. All of the other folders open up fine, and if you hover over the folder name, it displays the details of the contents of the folder (Messages: 65, Size: 11 MB) but no amount of clicking will open it - it just does nothing. Other users (like me) can open the folder just fine, and when the user shares the "Sent" folder, it can be accessed by others. Any ideas? We are running 5.0.1 FOSS Edition.

[pshah]

- Run the web client under Firefox,
- Append "?dev=1" to the url.
- Try to repro the bug.
- Open Tools > Error Console
- Click on "Errors" button in the toolbar or the Error Console window
- Report any javascript errors posted to this window as a result of clicking on the Sent folder

Thanks.

[Russianspi]

Umm...now I can't reproduce it - but what you are saying seems to be good advice for anything with the web client. Anyway, not being able to reproduce it means that it's solved, I guess. I'll keep your info gathering/troubleshooting technique tucked away in my pocket, however, and I'll use it next time I have a problem with the web client. Thanks!

[Rich Graves]

There is at least one magic number in the web client that can cause similar behavior: Bug 23860 - Zimlets being cached into global cache potentially cause conflict with mail item

[Russianspi]

Hmm. Looks like it will be fixed in 5.0.2. Hopefully I won't see this one again. Thanks!

[Russianspi]

I saw something similar this morning - Except that it was an E-mail, not a folder, and it actually threw an error this time. As instructed, I loaded Zimbra up in debug mode, and here's the error:

Body: {
  Fault: {
    Code: {
      Value: "soap:Receiver"
     },
    Detail: {
      Error: {
        Code: "service.FAILURE",
        Trace: "com.zimbra.common.service.ServiceException: system failure: java.lang.NullPointerException
Code:service.FAILURE
	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:183)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:365)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:208)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:113)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)
	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$CachedChain.doFilter(ServletHandler.java:1093)
	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
	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:205)
	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.lang.NullPointerException
	at com.zimbra.cs.mime.Mime.findStartBoundary(Mime.java:273)
	at com.zimbra.cs.mime.Mime.validateMultipart(Mime.java:244)
	at com.zimbra.cs.mime.Mime.getMultipartContent(Mime.java:482)
	at com.zimbra.cs.mime.Mime.handlePart(Mime.java:219)
	at com.zimbra.cs.mime.Mime.getParts(Mime.java:162)
	at com.zimbra.cs.service.mail.ToXML.encodeMessageAsMP(ToXML.java:733)
	at com.zimbra.cs.service.mail.GetMsg.handle(GetMsg.java:91)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)
	... 29 more
",
        _jsns: "urn:zimbra"
       }
     },
    Reason: {
      Text: "system failure: java.lang.NullPointerException"
     }
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    change: {
      token: 9818
     },
    sessionId: [
      0: {
        _content: "116040",
        id: "116040"
       }
     ]
   }
 },
_jsns: "urn:zimbraSoap"

Is this the aforementioned bug that has been fixed in (the hopefully soon-to-be-released) 5.0.2? A server restart fixed it, which was fine, 'cause it happened at about 6 a.m. (not a peak time here, by any means), but that's hardly an acceptable long-term solution.

By the way, I had the user share his inbox with me, so I could pull the same message for him, and I got the same error.