Results 1 to 5 of 5

Thread: Mobile Phone Browser - http://server/zimbra/m/ crashing

  1. #1
    liverpoolfcfan's Avatar
    liverpoolfcfan is offline Outstanding Member
    Join Date
    Oct 2009
    Location
    Dublin, IRELAND
    Posts
    712
    Rep Power
    6

    Default Mobile Phone Browser - http://server/zimbra/m/ crashing

    I began testing the Mobile Phone Browser access to ZCS today, and have had serious problems.

    I cannot get the page to load on either Windows Mobile 6 or Nokia Web Browsers.

    The Inbox page renders, then immediately starts to reload, this continues over and over.

    Here is a single instance of the error cut from the mailbox.log file

    Anybody got any bright ideas to fix or get around this ?

    I also tried to download the J2ME version of the mobile client to test that way of accessing - but the download page does not seem to be working.


    Code:
    2009-11-09 16:19:54,168 INFO  [btpool0-8://localhost/service/soap/SearchRequest] [name=users@server;mid=3;oip=192.168.200.20;ua=zclient/6.0.2_GA_1912.RHEL5_64;] soap - SearchRequest
    2009-11-09 16:19:54,168 INFO  [btpool0-8://localhost/service/soap/SearchRequest] [name=user@server;mid=3;oip=192.168.200.20;ua=zclient/6.0.2_GA_1912.RHEL5_64;] SoapEngine - handler exception
    com.zimbra.common.service.ServiceException: invalid request: unknown groupBy: 
    ExceptionId:btpool0-8://localhost/service/soap/SearchRequest:1257783594168:a99e93bd53f5f4da
    Code:service.INVALID_REQUEST
    	at com.zimbra.common.service.ServiceException.INVALID_REQUEST(ServiceException.java:254)
    	at com.zimbra.cs.index.MailboxIndex.parseTypesString(MailboxIndex.java:480)
    	at com.zimbra.cs.index.SearchParams.setTypesStr(SearchParams.java:175)
    	at com.zimbra.cs.index.SearchParams.parse(SearchParams.java:387)
    	at com.zimbra.cs.service.mail.Search.handle(Search.java:93)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:418)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:272)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:156)
    	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
    	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:379)
    	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:765)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:324)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:525)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:882)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:387)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

  2. #2
    daria is offline New Member
    Join Date
    May 2009
    Posts
    4
    Rep Power
    6

    Unhappy Us too

    We are having the same issue... Windows mobile 6.1 on an HTC tilt. the previous version of Zimbra mobile worked well.

    we recently upgraded and the mobile version is very flakey.

    the default view doesn't allow the user to see any navigation other than inbox/folders.

    The GPRS/Edge view does allow the user to see tabs for calendar, contacts, folders, and search.

    In either view, when one clicks on a message, it reloads and reloads and reloads. If one clicks on "preferences/version" it reloads and reloads also..

  3. #3
    cayaraa's Avatar
    cayaraa is offline Special Member
    Join Date
    Jul 2009
    Posts
    106
    Rep Power
    6

    Default

    I have a user with a Nokia that has the same problem (and I see the same error in the logs). He said it never happened when we were still on 5.x

  4. #4
    liverpoolfcfan's Avatar
    liverpoolfcfan is offline Outstanding Member
    Join Date
    Oct 2009
    Location
    Dublin, IRELAND
    Posts
    712
    Rep Power
    6

    Default

    Looks like a fix for this is coming in 6.0.4

    Bug 42322 – Mobile client throws error when opening messages within Nokia Browser.

    The bug details changes to 2 files. I was only able to download one of the two - zmain - with perforce. It alone stops the client from constantly looping.

    The Javascript file seem to also be needed but it has not been uploaded as yet.

    Hopefully when released it will fix these issues completely.

  5. #5
    daria is offline New Member
    Join Date
    May 2009
    Posts
    4
    Rep Power
    6

    Default

    Rock on... Until there we are using activesync and it seems to be working much better for the client.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 1
    Last Post: 12-17-2009, 09:42 AM
  2. Mobile browser calendar bug?
    By kevin1ab in forum Zimbra Mobile
    Replies: 2
    Last Post: 07-14-2008, 04:02 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •